From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Bug 10738 - Cannot set breakpoint on inlined function
Date: Fri, 03 Jun 2011 08:03:00 -0000 [thread overview]
Message-ID: <20110603080259.GB30867@host1.jankratochvil.net> (raw)
In-Reply-To: <BANLkTinNu_2FR4nYd2hxMyypz5wFMwDbzg@mail.gmail.com>
Hi Andrew,
On Sun, 29 May 2011 16:43:16 +0200, Andrew Cagney wrote:
> This bug apparently recently came up on the GCC lists, and RMS is
> drawing it to our attention. Does it pique anyone's interest?
>
> http://sourceware.org/bugzilla/show_bug.cgi?id=10738
while it is sure a high priority Bug it is meaningful only for interactive
debugging of -O2 -g code. AFAIK most of the GDB use cases is only for
backtracing, both automatic (ABRT, Apport, others) and by hand (bt+quit) as
people do not want to learn all the GDB commands.
-O2 -g interactive debugging (stepping) is not yet much feasible due to the
"jumping around" as GCC does not produce valid DW_LNS_negate_stmt and does not
properly undo/redo variable states by DWARF across scheduled instructions, as
planned by Alexandre Oliva.
The highest priority is to get at least the backtraces working for -O2 -g code.
For example archer-jankratochvil-entryval for it I will submit these weeks.
Thanks,
Jan
prev parent reply other threads:[~2011-06-03 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 14:43 Andrew Cagney
2011-06-03 8:03 ` Jan Kratochvil [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=20110603080259.GB30867@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=cagney@gnu.org \
--cc=gdb@sourceware.org \
/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).