public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com, Roland McGrath <roland@redhat.com>
Subject: Re: Identifying bottom-of-stack
Date: Wed, 04 Aug 2004 17:17:00 -0000	[thread overview]
Message-ID: <20040804171602.GA18438@nevyn.them.org> (raw)
In-Reply-To: <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

  reply	other threads:[~2004-08-04 17:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 16:01 Andrew Cagney
2004-08-04 17:17 ` Daniel Jacobowitz [this message]
2004-08-04 18:12   ` Andrew Cagney
2004-08-04 18:03     ` Daniel Jacobowitz
2004-08-04 18:31       ` Andrew Cagney
2004-08-04 19:02 ` Roland McGrath
2004-08-05  9:42   ` Mark Kettenis
2004-08-05 13:03     ` Andrew Cagney
2004-08-05 20:18     ` Roland McGrath
2004-08-11 17:51       ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040804171602.GA18438@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=roland@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).