DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=FX
	rXBehymZbKaGzGgs6iEsn4Md+JcepsZ8/GmvtGYI7zvXaLq/zBnzOiGYqKAEvZK7
	k5Dr8ix1ADwcPRaHJEQ7h26ns6+jzc3MfukS2XymYej5lT3T0pqGjs7sIT/j4EqW
	Vu2PHcfnRH843DA0LZOZ5nx0itmVusSX5rXfEqydo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <55BA373A.4020909@dronecode.org.uk>
References: <CAOC2fq_fahjLapKbgO8Xer8neEjv1Ohs4bM3JOWcka0ajjcbCg@mail.gmail.com>	<55BA373A.4020909@dronecode.org.uk>
Date: Thu, 30 Jul 2015 10:46:20 -0700
Message-ID: <CAOC2fq-ET7BmUQYOLXV_w_QMZE1rfZ8_JpJvVGF=nDS7gTaWWA@mail.gmail.com>
Subject: Re: Analyzing a SEG FAULT that gdb doesn't help with
From: Michael Enright <mike@kmcardiff.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

On Thu, Jul 30, 2015 at 7:39 AM, Jon TURNEY  wrote:
> You need to install the 'cygwin-debuginfo' package for debug symbols for
> cygwin1.dll

I missed this in my searches. I see now that I should have used the
"debug" category.

>
> 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
> /usr/src/debug/cygwin-2.1.0-1/newlib/libc/machine/i386/strlen.S:64

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
libmozjs185) with several extensions to JavaScript in order to emulate
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
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple