This is the mail archive of the
mailing list for the Cygwin project.
Am set up for debugging... what next.
- To: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Subject: Am set up for debugging... what next.
- From: Troy Noble <troy dot noble at channelpoint dot com>
- Date: Mon, 23 Apr 2001 15:56:49 -0600
OK, I followed directions that Egor, Christopher, and DJ Delorie provided.
And now I need a little more direction.
- grabbed the latest DLL sources
- created an /obj directory, then ran
/src/configure --enable-debugging --prefix=/install
- did a make
- copied gdb.exe and known-good (i.e. OLD) cygwin1.dll to /gdb-working
- shut everything down and copied the new-cygwin1.dll over cygwin1.dll
- created a /gdb-working/startup_gdb.cmd that reads:
c:\gdb-working\gdb.exe %1 %2
- in my .basrhc I set:
and started a new bash window of course, echo $CYGWIN
Now I run:
$ sleep 30 &
$ kill -11 <PID of the sleep 30 command here>
I see: + Segmentation fault sleep 30
Shouldn't gdb pop up at this point?
What am I missing here?
Apologies if this is the wrong list. Looked like the description
of cygwin-developers was for hard-core folks not just hobbyists
like myself who were trying to get to the root of a common
Access Violation so they can get back to being a user ;->
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple