From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: RFC: preserve line number when skipping prologue
Date: Fri, 27 Mar 2009 16:00:00 -0000 [thread overview]
Message-ID: <20090327155506.GS9472@adacore.com> (raw)
In-Reply-To: <20090327021842.GA29050@caradoc.them.org>
> FWIW, a (related) request we often see is for IDEs to report which
> lines can have breakpoints set on them. Still not foolproof with
> optimized code, but much better. Eclipse JDT (Java) does this, and I
> believe at least one vendor has managed to get CDT to do it also.
I guess the way they do it is by doing a reverse lookup after having
inserted the breakpoint (by using the "info line *ADDR" or its MI
equivalent)? For IDEs, we could perhaps enhance the output to include
the actual line if different from the requested one.
Or, we could decide to change the break command to report the
actual line. I can poll the AdaCore engineers :).
--
Joel
prev parent reply other threads:[~2009-03-27 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 21:06 Tom Tromey
2009-03-26 23:10 ` Joel Brobecker
2009-03-26 23:45 ` Tom Tromey
2009-03-27 0:46 ` Joel Brobecker
2009-03-27 2:19 ` Daniel Jacobowitz
2009-03-27 16:00 ` Joel Brobecker [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=20090327155506.GS9472@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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