Re: Suggestion: backtrace stop guard for threads callstacks

[Joel Brobecker <brobecker@adacore.com>]

> FYI, this is discussed here about five times a year in one form or
> another.

Yes, I remember now. But ...

> For systems we control, the correct solution is not this at
> all, but to add unwinding information or suitable prologues that
> indicate the end of the stack.  Almost every architecture has a
> suitable sequence, and we have a recently-decided-upon DWARF convention
> to represent it also.

I understand. But I also thought that it would be nice to avoid printing
the frames that are relative to thread startup code, and start the
backtrace at the function the code used in the pthread_create call
for instance. I think that the user won't be interested in them most
of the time.

That was part of my motivation. No big deal, I'll solve the other
issues the recommended way the next time I come across them.

-- 
Joel