From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: brobecker@gnat.com, kettenis@chello.nl
Cc: cagney@gnu.org, eliz@gnu.org, gdb@sources.redhat.com, hjl@lucon.org
Subject: Re: [6.2] PROBLEMS file
Date: Fri, 23 Jul 2004 05:44:00 -0000 [thread overview]
Message-ID: <20040723004654.8B6A04B104@berman.michael-chastain.com> (raw)
joel> FWIW: As a user, I don't mind when the unwinder goes too far and
joel> displays too many frames. The info we're looking for is there, and
joel> that's what really counts for me. Not pretty, but good enough.
joel> So I wouldn't mind closing that particular PR, especially since
joel> there doesn't seem to be any accurate way of detecting the top
joel> of the call stack.
There are really two separate problems here. gdb/1505 is all about
top-of-stack detection. How about we document the limitation and
live with it.
The existing text is:
Most programs have a standard user entry point---a place where system
libraries and startup code transition into user code. For C this is
@code{main}. When @value{GDBN} finds the entry function in a
backtrace it will terminate the backtrace, to avoid tracing into highly
system-specific (and generally uninteresting) code.
How about adding something like this:
@value{GDBN} is not perfect at detecting the top of the call stack.
For instance, if your program creates multiple threads, then the
stack of an individual thread may not start with @code{main} at all.
So you may see strange frames at the top of the stack; it is safe to
ignore these.
If we document it, I am okay with closing the PR.
(And while I was reading the doco I noticed "set backtrace limit" is
already implemented, which is exactly what I want for callfuncs.exp!)
The other problem is strange frames in the middle that cause the
trace to go bad before it gets to any interesting user code.
That's a different, and much worse, problem, but it's not PR gdb/1505.
See PR gdb/1255 and PR gdb/1253. Those two particular PR's have been
fixed.
Michael C
next reply other threads:[~2004-07-23 0:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 5:44 Michael Elizabeth Chastain [this message]
2004-07-23 20:44 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-07-22 12:14 Michael Elizabeth Chastain
2004-07-22 18:28 ` Joel Brobecker
2004-07-22 19:26 ` Eli Zaretskii
2004-07-22 20:51 ` Mark Kettenis
2004-07-23 9:24 ` Eli Zaretskii
2004-07-23 11:22 ` Mark Kettenis
2004-07-23 12:03 ` Eli Zaretskii
2004-07-23 12:13 ` Eli Zaretskii
2004-07-23 12:16 ` Dave Korn
2004-07-23 13:36 ` Mark Kettenis
2004-07-23 16:17 ` Eli Zaretskii
2004-07-19 3:51 Andrew Cagney
2004-07-19 21:01 ` Eli Zaretskii
2004-07-21 21:12 ` Mark Kettenis
2004-07-21 22:05 ` H. J. Lu
2004-07-22 20:58 ` Mark Kettenis
2004-07-22 21:33 ` Joel Brobecker
2004-07-22 21:38 ` H. J. Lu
2004-07-21 22:17 ` Andrew Cagney
2004-07-22 7:13 ` Eli Zaretskii
2004-07-22 13:04 ` Dave Korn
2004-07-22 15:17 ` Daniel Jacobowitz
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=20040723004654.8B6A04B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=kettenis@chello.nl \
/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).