On Tue, 14 Oct 2003, Robb, Sam wrote: > Hope this helps some... > > $ gdb --pid=1224 > At least the stack trace part doesn't. You attached to the bash exec stub of cygpath, not cygpath itself. There are already several of these back traces in the archives.
The actual cygpath is here: > Process: cygpath.exe Pid: 1280 > Maybe all that DLL info is useful to a more trained eye. I don't know. > Path Description Company Name Version > <Unable to query process module information> > C:\WINNT\system32\locale.nls > C:\WINNT\system32\sortkey.nls > C:\WINNT\system32\sorttbls.nls > C:\WINNT\system32\unicode.nls > I got this too and figured it would not be of much use, so I didn't bother including it. The handle information might be interesting, though. > ---------------------------------------- > > Handle information for cygpath.exe: > > ---------------------------------------- > > Process: cygpath.exe Pid: 1280 > > Type Name > Desktop \Default > Directory \Windows > Directory \KnownDlls > File \Device\Afd\Endpoint > File C:\cygwin > File \Device\NamedPipe\Win32Pipes.000004c0.00000001 > File C:\cygwin\var\log\setup.log.postinstallXa00660 > File \Device\NamedPipe\Win32Pipes.000004c0.00000001 > Key HKLM > Mutant \BaseNamedObjects\DBWinMutex > Process bash.exe(1232) > Process bash.exe(1232) > Process bash.exe(1216) > Section \BaseNamedObjects\cygpid.4D0 > Section > \BaseNamedObjects\cygwin1S3.S-1-5-21-313501798-2004386012-1271835937-1626.27 > Section \BaseNamedObjects\cygwin1S3.shared.3 > Here are the two WindowStation handles I mentioned. Maybe this is normal. I don't know. > WindowStation \Windows\WindowStations\WinSta0 > WindowStation \Windows\WindowStations\WinSta0 > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- 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/
