This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Identifying bottom-of-stack
- From: Daniel Jacobowitz <drow at false dot org>
- To: Andrew Cagney <cagney at gnu dot org>
- Cc: gdb at sources dot redhat dot com, Roland McGrath <roland at redhat dot com>
- Date: Wed, 4 Aug 2004 13:16:02 -0400
- Subject: Re: Identifying bottom-of-stack
- References: <41110832.7040104@gnu.org>
On Wed, Aug 04, 2004 at 12:00:50PM -0400, Andrew Cagney wrote:
> Hello,
>
> In the multi-threaded case, GDB's having fun identifying the outer-most
> (oldest) frame and, unfortunatly, has this habit of backtracing past it :-/
>
> Does anyone see a problem with:
>
> - GLIBC marking those outermost frames with CFI indicating that both the
> CFA and the RA are "unknown"?
>
> - GDB's CFI unwinder recognizing this and returning a NULL frame ID (gdb
> doesn't unwind _past_ such a frame).
>
> I think this would give us a portable way of terminating the stack.
>
> comments?
This would make debugging in the outermost frame quite annoying,
wouldn't it? We won't be able to find any frame relative variables.
I realize users rarely need to do this, but if we're going to design a
solution it should take this into account.
--
Daniel Jacobowitz