From: Mark Kettenis <kettenis@chello.nl>
To: dann@ics.uci.edu
Cc: gdb@sources.redhat.com
Subject: Re: [HEADS UP] Merging i386newframe into mailine
Date: Sat, 24 May 2003 11:15:00 -0000 [thread overview]
Message-ID: <200305241115.h4OBFYVP025439@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <200305231745.h4NHj2JL029521@gremlin.ics.uci.edu> (message from Dan Nicolaescu on Fri, 23 May 2003 10:45:00 -0700)
From: Dan Nicolaescu <dann@ics.uci.edu>
Date: Fri, 23 May 2003 10:45:00 -0700
Hi!
First of all thanks for all the great work you have been doing on x86
debugging!
Would you mind posting something on the mailing list statement about
what does this imply WRT debugging frameless code.
Would this allow GCC to enable -momit-leaf-frame-pointer by default?
How about -fomit-frame-pointer ?
Any of this would be great, and probably nobody would mind delaying a
release if this was going to happen...
Assuming that GCC generates the correct debug info, yes this would
allow GDB to debug -fomit-frame-pointer code. So this would only work
with -gdwarf-2, or when DWARF2 is the default debug info (which I
think is true for most ELF targets since GCC 3.2).
AFAICT GCC 3.2.2 generates the corredt DWARF CFI info, so backtraces
should work. However, I'm not sure whether GCC generates the correct
debug info for function arguments and local variables. Running the
testsuite with -fomit-frame-pointer produces many failures. However,
this appears to be caused by GDB not finding the correct first line of
a function.
We're not quite there yet :-(.
Mark
prev parent reply other threads:[~2003-05-24 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 16:52 Mark Kettenis
2003-05-23 17:15 ` Andrew Cagney
2003-05-24 9:52 ` Eli Zaretskii
2003-05-24 11:27 ` Mark Kettenis
2003-05-24 17:38 ` Eli Zaretskii
2003-05-26 15:31 ` Andrew Cagney
2003-05-29 15:14 ` Mark Kettenis
2003-05-29 16:48 ` Andrew Cagney
[not found] ` <200305231745.h4NHj2JL029521@gremlin.ics.uci.edu>
2003-05-24 11:15 ` Mark Kettenis [this message]
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=200305241115.h4OBFYVP025439@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=dann@ics.uci.edu \
--cc=gdb@sources.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).