Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jakob Engblom" <jakob@virtutech.com>
To: "'Michael Snyder'" <msnyder@vmware.com>,
		"'Pedro Alves'" <pedro@codesourcery.com>
Cc: "'Eli Zaretskii'" <eliz@gnu.org>, 	<teawater@gmail.com>,
		<gdb-patches@sourceware.org>, 	<brobecker@adacore.com>
Subject: RE: [RFA] Displaced stepping just enable in non-stop mode
Date: Fri, 17 Oct 2008 19:47:00 -0000	[thread overview]
Message-ID: <00df01c93091$1b2d3af0$5187b0d0$@com> (raw)
In-Reply-To: <48F8CB7E.3060102@vmware.com>

> > I see, then this means that all the reverse targets in existance
> > implement inserting breakpoints (target_insert_breakpoint, Z packet),
> > instead of relying on memory breakpoints.
> 
> I believe that's true.  Certainly it's true for gdb-freeplay.

Do I understand to mean that the assumption is that the remote-capable target
system 
Implements breakpoints by NOT modifying the code, but rather using some other
mechanism that says that certain instructions in memory are breakpoints, and
triggers them appropriately? 

This is what we do in Simics, and this assumptions makes sense to us.
Breakpoints are implemented in the simulator, without any change to the target
system. 

/jakob


  reply	other threads:[~2008-10-17 19:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07  6:27 teawater
2008-10-07 12:18 ` Joel Brobecker
2008-10-08  6:11   ` teawater
2008-10-09 14:50     ` Pedro Alves
2008-10-10  3:38       ` teawater
2008-10-14  7:36         ` teawater
2008-10-16  0:07           ` Pedro Alves
2008-10-16  2:29             ` teawater
2008-10-16  2:39             ` Daniel Jacobowitz
2008-10-16  2:59               ` Pedro Alves
2008-10-22  3:16                 ` teawater
2008-10-22 19:48                   ` Eli Zaretskii
2008-10-23  8:13                     ` teawater
2008-10-23 12:57                       ` Pedro Alves
2008-10-24  2:49                         ` teawater
2008-10-16  8:13             ` Eli Zaretskii
2008-10-16 12:35               ` Daniel Jacobowitz
2008-10-16 18:27                 ` Eli Zaretskii
2008-10-16 18:33                   ` Daniel Jacobowitz
2008-10-16 21:19                     ` Michael Snyder
2008-10-17  5:46                       ` teawater
2008-10-17 10:02                         ` Eli Zaretskii
2008-10-17 15:05                           ` Pedro Alves
2008-10-17 16:09                           ` teawater
2008-10-17 14:48                       ` Pedro Alves
2008-10-17 16:01                         ` teawater
2008-10-17 17:33                         ` Michael Snyder
2008-10-17 19:47                           ` Jakob Engblom [this message]
2008-10-17 19:49                             ` Michael Snyder
2008-10-17 14:51                   ` Pedro Alves
2008-10-17 15:53                     ` Eli Zaretskii

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='00df01c93091$1b2d3af0$5187b0d0$@com' \
    --to=jakob@virtutech.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.com \
    --cc=teawater@gmail.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