Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: Wed, 8 Oct 2003 15:02:00 -0400
From: Christopher Faylor <cgf-rcm AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygpath hang - using gdb
Message-ID: <20031008190200.GB30340@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20031008183653 DOT GB29282 AT redhat DOT com> <NGBBLLIAMFLGJEOAJCCEAEAGDFAA DOT garbage_collector AT telia DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NGBBLLIAMFLGJEOAJCCEAEAGDFAA.garbage_collector@telia.com>
User-Agent: Mutt/1.4.1i

On Wed, Oct 08, 2003 at 08:53:45PM +0200, Hannu E K Nevalainen wrote:
>
>> -----Original Message-----
>> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
>> Of Christopher Faylor
>> Sent: Wednesday, October 08, 2003 8:37 PM
>> To: cygwin AT cygwin DOT com
>> Subject: Re: cygpath hang - using gdb
>>
>>
>> On Wed, Oct 08, 2003 at 08:00:21PM +0200, Hannu E K Nevalainen wrote:
>> >> I will be investigating the problem in every way that anyone can
>> >> think of as time permits. No promises though, as usual.
>> >> I'll have to learn bits and pieces of cvs and gdb for starters -
>> >> I'll do my best.
>> >
>> >$ MODE=ironic rant
>> >
>> > "I'll be back" - is this a general salute nowadays? ;-P
>> >
>> >You're about to see me trying to use gdb for the first time. Say after me
>> >please: "YES, WE LOVE IT!" ...  Ahh... I didn't hear you ;-)
>> >
>> >$ MODE=serious
>> >
>> >Looking at "sample use" in "info gdb" I see things that looks fairly
>> >straight forward and familiar. Now when I try "gdb --pid=<cygpath pid>" -
>> >when cygpath has hung - I end up with a situation that I don't recognise
>> >from that sample.
>> >
>> >A couple of "s" commands and the gdb session ends up having no "(gdb)"
>> >prompt. I get the impression that cygpath has stopped somewhere
>> in a system
>> >DLL, and debugging fails in there. Killing cygpath makes the
>> prompt return.
>>
>> No, you've stepped into the part that is hanging, so gdb is
>> waiting patiently
>> for it to return.
>>
>> cgf
>
>Ok. Got that.
>Now; Any ideas how to work further on this?
>Set breakpoints at "random" places in cygpath?

Build a cygwin1.dll with --enable-debugging, install it, build cygpath.exe,
install it.  "set CYGWIN_DEBUG=cygpath" at the command prompt before running
setup.exe.  That will pop up a debugger when cygpath is run before main is
hit.

cgf

--
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/