From: Daniel Jacobowitz <drow@false.org>
To: Ross Morley <ross@tensilica.com>
Cc: gdb@sourceware.org
Subject: Re: RFC: Program Breakpoints
Date: Tue, 24 Mar 2009 20:40:00 -0000 [thread overview]
Message-ID: <20090324203953.GA309@caradoc.them.org> (raw)
In-Reply-To: <49C94379.3020206@tensilica.com>
On Tue, Mar 24, 2009 at 01:32:57PM -0700, Ross Morley wrote:
>> I read through this; overall, it looks sane. On some targets
>> implementing this would require the remote stub to read from pc
>> anyway; that's faster than GDB doing it, but not necessarily much
>> faster. But on some other targets the stub has to do this anyway,
>> or can pipeline it with other necessary operations, so it's not a big
>> loss.
>>
>>
>
> I think you're saying it's not a big deal performance-wise to do this
> without a remote protocol extension. Is that correct?
No, I was saying the opposite. Sometimes it will still be expensive
to implement the protocol extension. I'm interested in whether anyone
sees an approach that does not require instruction scanning.
GDB has the option to cheat - it can consult the program (ELF file),
separately from the target's view of memory. This would not work for
stray breakpoints inserted in the program at runtime, though.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-03-24 20:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 17:41 [RFC] stepping over permanent breakpoint Aleksandar Ristovski
2009-03-16 18:22 ` Pedro Alves
2009-03-16 18:55 ` Aleksandar Ristovski
2009-03-16 19:38 ` Pedro Alves
2009-03-16 20:37 ` Aleksandar Ristovski
2009-03-16 18:50 ` Mark Kettenis
2009-03-16 19:04 ` Aleksandar Ristovski
2009-03-23 16:50 ` RFC: Program Breakpoints (was: [RFC] stepping over permanent breakpoint) Ross Morley
2009-03-24 16:57 ` Daniel Jacobowitz
2009-03-24 20:33 ` RFC: Program Breakpoints Ross Morley
2009-03-24 20:40 ` Daniel Jacobowitz [this message]
2009-03-24 23:48 ` Pedro Alves
2009-03-25 7:58 ` Mark Kettenis
2009-03-25 13:17 ` Pedro Alves
2009-03-24 23:59 ` Ross Morley
2009-03-31 0:44 ` Ross Morley
2009-03-31 3:17 ` 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=20090324203953.GA309@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=ross@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