Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 18 Jul 2003 10:11:47 +0100 (BST) From: andrew brian clegg X-X-Sender: fcleg01 AT sark DOT cryst DOT bbk DOT ac DOT uk To: "'cygwin AT cygwin DOT com'" Subject: Re: tar 1.13.25 runs forever and produces nothing on this test ca se In-Reply-To: <3F16F552.8010403@cygwin.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact CCSG (http://www.cryst.bbk.ac.uk/CCSG/) more information X-MailScanner-cryst-bbk: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-31, required 9, BAYES_01, EMAIL_ATTRIBUTION, FROM_ENDS_IN_NUMS, IN_REP_TO, QUOTED_EMAIL_TEXT, REPLY_WITH_QUOTES, USER_AGENT_PINE) Larry, Can I just jump in here and say thanks for doing this quick intro to debugging? The closest I've come to gcc and gdb was using DJGPP about eight years ago and it's hard to know where to start when things go wrong. This should get me started next time something does... Andrew. On Thu, 17 Jul 2003, Larry Hall wrote: > Date: Thu, 17 Jul 2003 15:13:22 -0400 > From: Larry Hall > Reply-To: cygwin AT cygwin DOT com > To: "Biederman, Steve" > Cc: "'cygwin AT cygwin DOT com'" > Subject: Re: tar 1.13.25 runs forever and produces nothing on this test > ca se > > We'll make a developer out of you yet! :-) > > You'll need to run setup and install the 'gcc' package (not > gcc2) and the 'gdb' package. That should install everything > you need as a build environment. You'll also want the source > for tar. Get that from setup too. Once done installing, > do the following: > > 1. cd /usr/src/tar-1.13.25-1/ > 2. ./configure CFLAGS=-g > 3. make > > Now you can try this version to see if your problem reproduces. > The new 'tar' is in ./src. If you can reproduce the problem there, > try it in gdb. To do so, type 'gdb src/tar.exe'. At the gdb prompt, > type 'r the problem>'. This will start it running. When you think it's to > the point where it's hanging, type ctrl-c to stop it and then 'bt'. > This will tell you where you are. You can step through the code with > 'n'. Presumably, you'll see you're cycling through the same statements > at some point. > > This may not point out the source of the problem to you, although > you'll have more information to report to the list about the case > you're running into. The steps you took, things you saw, and the > result of 'bt' (initially at least) may help someone on this list > spot your problem. > > Good luck and enjoy! ;-) > > Larry > > > Biederman, Steve wrote: > > > Which I've never done; I'm not a cygwin developer, just a user. > > Do you remember where cygwin documents how to set up a build environment > > and get a build going? > > > > > > -----Original Message----- > > From: Larry Hall [mailto:cygwin-lh AT cygwin DOT com] > > Sent: Thursday, July 17, 2003 11:00 AM > > To: Biederman, Steve > > Cc: 'cygwin AT cygwin DOT com' > > Subject: Re: tar 1.13.25 runs forever and produces nothing on this test > > ca se > > > > > > Biederman, Steve wrote: > > > > > >>Any suggestions how I can proceed to debug why tar acts the way it does for me and > >>not for you? > > > > > > > > I think you're down to building and debugging the code. > > > > > -- > Larry Hall http://www.rfk.com > RFK Partners, Inc. (508) 893-9779 - RFK Office > 838 Washington Street (508) 893-9889 - FAX > Holliston, MA 01746 > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/