From: Doug Evans <dje@google.com>
To: Raphael Zulliger <zulliger@indel.ch>
Cc: Yao Qi <yao@codesourcery.com>, gdb <gdb@sourceware.org>
Subject: Re: Unneeded displaced single stepping causes issues: Performance drop and range stepping killer
Date: Wed, 01 May 2013 03:36:00 -0000 [thread overview]
Message-ID: <CADPb22SfwjJW1yVd1EE1fOVGp3X9Y_4=1ZgvCgo-3GcUWDkQQg@mail.gmail.com> (raw)
In-Reply-To: <51778299.40402@indel.ch>
On Tue, Apr 23, 2013 at 11:58 PM, Raphael Zulliger <zulliger@indel.ch> wrote:
> - There's something I hope we could improve (but I haven't looked
> into the code yet): When GDB receives a stop reply, it issues many "memory
> reads". Sometimes it read consecutive memory by multiple RSP packages.
> Sometime it even reads the same memory region twice.
It's unfortunate that gdb's remote caching support doesn't work better
"out of the box".
next prev parent reply other threads:[~2013-05-01 3:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 10:54 Raphael Zulliger
2013-04-23 19:03 ` Pedro Alves
2013-04-24 6:58 ` Raphael Zulliger
2013-04-24 2:24 ` Yao Qi
2013-04-24 6:58 ` Raphael Zulliger
2013-05-01 3:36 ` Doug Evans [this message]
2013-05-03 2:32 ` Yao Qi
2013-04-24 4:54 ` Tom Tromey
2013-04-24 6:58 ` Raphael Zulliger
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='CADPb22SfwjJW1yVd1EE1fOVGp3X9Y_4=1ZgvCgo-3GcUWDkQQg@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=yao@codesourcery.com \
--cc=zulliger@indel.ch \
/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