This is the mail archive of the
mailing list for the Cygwin project.
Re: bash, dircolors, setsid and a stackdump
- From: David Rothenberger <daveroth at acm dot org>
- To: cygwin at cygwin dot com
- Date: Thu, 22 Jan 2004 17:37:23 -0800
- Subject: Re: bash, dircolors, setsid and a stackdump
- References: <Law9-OE408FeHQYTTIA00007be5@hotmail.com>
Rafael Kitover wrote:
I would dearly love to know how you get those lovely line numbers in the
I used the unstripped DLL from my CVS build and then used addr2line on
each function address in the stacktrace, specifying the DLL as the
addr2line -e /bin/cygwin1.dll <ADDRESS>
I don't know whether it's necessary to be running the unstripped DLL when
the stacktrace is generated, but I was.
I have since discovered that while dircolors does cause the stackdump, the
problem is not dircolors. With that line commented from /etc/profile, I
don't get a stackdump but the script does not complete its execution. I
determined this by executing the script
echo foo > t
and noting that t was created but of zero length.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html