This is the mail archive of the
mailing list for the Cygwin project.
Re: bash, dircolors, setsid and a stackdump
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: David Rothenberger <daveroth at acm dot org>
- Cc: cygwin at cygwin dot com
- Date: Thu, 22 Jan 2004 21:01:53 -0500 (EST)
- Subject: Re: bash, dircolors, setsid and a stackdump
- References: <Law9-OE408FeHQYTTIA00007be5@hotmail.com> <40107AD3.firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On Thu, 22 Jan 2004, David Rothenberger wrote:
> Rafael Kitover wrote:
> > I would dearly love to know how you get those lovely line numbers in the
> > stackdump :)
> 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
> executable. I.e.,
> 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.
It is. If you think about it, it's rather obvious... If you run one DLL
and then use another as the executable for addr2line, the addresses are
all going to be different.
> 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.
Hmm... Note that to use the dircolors file, one needs to do a back-quote
substitution. Just an observation.
> I determined this by executing the script
> ---begin script---
> echo foo > t
> sleep 10
> ---end script---
> and noting that t was created but of zero length.
|\ _,,,---,,_ email@example.com
ZZZzz /,`.-'`' -. ;-;;,_ firstname.lastname@example.org
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html