> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Christopher Faylor > Sent: Wednesday, October 08, 2003 8:37 PM > To: [EMAIL PROTECTED] > 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? I've been persuing a display of source to get a grip on what and where things are happening, but that seems to be totally over my head at the moment. Probable cause: I don't know a single thing about Windows nor Cygwin internals - and I'm seeing nothing but those parts of memory. /Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E -- UTC+01, DST -> UTC+02 -- --END OF MESSAGE-- -- 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/