Re: Suggestion: backtrace stop guard for threads callstacks

["Jim Blandy" <jimb@red-bean.com>]

On 3/2/06, Andrew STUBBS <andrew.stubbs@st.com> wrote:
> 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.

That's certainly easy to do.  But it's clearly preferable for people
to properly mark their thread start functions.  If I'm remembering
right, we haven't yet seen any reports of this problem in cases where
we couldn't get the thread start function marked.  So I'd argue we
don't have any situations where this command was needed --- only cases
where using it would have helped people paper over an underlying
problem that needs to be fixed elsewhere.

Given how often this comes up, would it make sense to add an appendix
to the GDB manual explaining how to terminate backtraces?