Re: Option to disable frame checking

[Joel Brobecker <brobecker@adacore.com>]

> I do not know about Go alternate stacks but the checks for example
> already supports gcc -fsplit-stack.

I think we're both talking about the same feature - I couldn't remember
the exact technical term used for Go.

> More such features should be rather implemented than to drop
> UNWIND_INNER_ID.  Could not be GDB taught about thue alternate stack?
> 
> Looping backtraces are a pain for both interactive and automatic
> bugreporting, it is already a TODO item GDB should better handle f() {
> f(); } type stack overflows as it proven less GDB-savvy users fail to
> debug such issue in GDB.

Personally, I don't think tha the check and associated warning brings
anything extra. Getting a cryptic warning about some frame being inner
than another never really helped me more than getting a botched backtrace.
On the other hand, determining that a frame fails that invariant should
be relatively straightforward, thanks to the "info frame" command. Hence
the suggest to toss the check.

But if people prefer to keep the check, and have a technical way of
handling this sort of issue, then why not.
-- 
Joel