This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: bash, dircolors, setsid and a stackdump

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---
> #!/bin/sh
> echo foo > t
> sleep 10
> ---end script---
> and noting that t was created but of zero length.
> Dave

      |\      _,,,---,,_
ZZZzz /,`.-'`'    -.  ;-;;,_
     |,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:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]