This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Segfault in Cactid
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Fri, 2 Sep 2005 11:11:17 +0100
- Subject: RE: Segfault in Cactid
----Original Message----
>From: Larry Adams
>Sent: 02 September 2005 10:48
> Brian Dessent <brian <at> dessent.net> writes:
>
>>
>> Larry Adams wrote:
>>
>>> So my questions are: How do I trace the memory location above to a
>>> known system call using gdb? When, I attach to my hung process, what
>>> should I be doing to determine the calling/offending function.
>>
>> Build a cygwin1.dll with debug symbols and then use addr2line. Or use
>> strace. At the very least you should try the latest snapshot to see if
>> it fixes your problem.
>>
>
> Brian, I am assuming that I can just download the latest cygwin of winsup
> and then configure/make. What configure/make options should I be using to
> incorporate debug symbols?
I may not be Brian, but I like to use
make CPPFLAGS_FOR_TARGET='-g -O0' CFLAGS_FOR_TARGET='-g -O0'
CXXFLAGS_FOR_TARGET='-g -O0' all 2>&1 | tee build.log
which gets you an unoptimised debug build. Killing optimisation makes
stepping through the source much easier as it doesn't jump around all over
the place.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
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/