Re: Suggestion: backtrace stop guard for threads callstacks

[Andrew STUBBS <andrew dot stubbs at st dot com>]

Daniel Jacobowitz wrote:
> FYI, this is discussed here about five times a year in one form or
> another.  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.

Yes, I started this same discussion last autumn. We finally decided that 
the Right Thing would be to do something to the library that creates the 
thread stack.

But, while we are having ideas....

How about:

set backtrace main-functions main;mytaskfunc;_start

or perhaps:

set backtrace add-main-function mytaskfunc

so that the user can stop backtraces whereever is appropriate for their 
environment.


Just a thought.

Andrew