Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Maxim Grigoriev <maxim@tensilica.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Marc Gauthier	<marc@tensilica.com>
Subject: Faster stepping amidst breakpoints
Date: Sat, 22 Jan 2011 15:06:00 -0000	[thread overview]
Message-ID: <4D3A114D.7010301@tensilica.com> (raw)

Hello GDB community,

Has anyone tried to optimize the GDB protocol by letting
the remote agent plant and unplant breakpoints when the
target resumes and stops, rather than having GDB do it
over the wire with round-trip latency on every single
breakpoint plant&  unplant request?

Certain GDB operations involve a lot of single-stepping,
which can be really slow on certain targets (especially
embedded targets) because of that latency.

In principle, GDB can query the remote agent to decide
whether to apply this optimization.  And the remote agent
must be careful not to plant any breakpoint at the current
PC when single-stepping.  There are likely other
considerations, but at a glance, it seems doable.
So am curious whether there's any particular reason
it wasn't done (that we could see).

Thanks,
-- Maxim



             reply	other threads:[~2011-01-21 23:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22 15:06 Maxim Grigoriev [this message]
2011-01-24  8:04 ` Daniel Jacobowitz
2011-01-24 21:08   ` Maxim Grigoriev
2011-01-31  7:47   ` Joel Brobecker
2011-01-31 15:39     ` Daniel Jacobowitz
2011-02-01  3:23       ` Joel Brobecker
2011-02-01 18:44         ` Michael Snyder
2011-02-03  4:55           ` Joel Brobecker
2011-02-02 17:10         ` Daniel Jacobowitz
2011-02-03  4:46           ` Joel Brobecker
2011-02-13 15:17         ` Mark Kettenis
2011-02-14  3:27           ` Joel Brobecker
2011-02-14 10:50             ` Joel Brobecker
2011-02-01 15:12       ` Pedro Alves
2011-02-03 22:54     ` Maxim Grigoriev
2011-02-04 16:06       ` Tom Tromey
2011-02-04 19:32         ` Maxim Grigoriev
2011-02-04 16:33       ` 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=4D3A114D.7010301@tensilica.com \
    --to=maxim@tensilica.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc@tensilica.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