This is the mail archive of the
mailing list for the Cygwin project.
Re: Analyzing a SEG FAULT that gdb doesn't help with
- From: Michael Enright <mike at kmcardiff dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 30 Jul 2015 10:46:20 -0700
- Subject: Re: Analyzing a SEG FAULT that gdb doesn't help with
- Authentication-results: sourceware.org; auth=none
- References: <CAOC2fq_fahjLapKbgO8Xer8neEjv1Ohs4bM3JOWcka0ajjcbCg at mail dot gmail dot com> <55BA373A dot 4020909 at dronecode dot org dot uk>
On Thu, Jul 30, 2015 at 7:39 AM, Jon TURNEY wrote:
> You need to install the 'cygwin-debuginfo' package for debug symbols for
I missed this in my searches. I see now that I should have used the
> You also need to point addr2line at those detached debug symbols, as (unlike
> gdb) it doesn't follow .gnu_debuglink pointers.
> (I'm assuming you've typoed 6155d363 here and it should be 0x6115D363 as the
> strace output says)
I've been having trouble getting that number right
> # addr2line -e /usr/lib/debug/usr/bin/cygwin1.dbg 0x6115D363
Another problem is that there's only one stack frame in the stack
dump, so knowing that it's a strlen just means I have to crank out
some grep commands and hopefully one of them is vulnerable to a
special case that now happens all the time.
> Are you sure the crashing process is the direct
> inferior of gdb, and not some wrapper process which runs it? (uninstalled
> libtool generated binaries do this, for e.g.)
The crashing executable is just a client of SpiderMonkey (via
some of the Windows cscript utility and to emulate another environment
that happens to be a massive annoyance to run scripts in. The
executable is built using a textbook Makefile.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple