From: Daniel Jacobowitz <drow@false.org>
To: Mathieu Lacage <Mathieu.Lacage@sophia.inria.fr>
Cc: gdb@sourceware.org
Subject: Re: help string for "break" command
Date: Fri, 12 Jan 2007 13:49:00 -0000 [thread overview]
Message-ID: <20070112134932.GA21726@nevyn.them.org> (raw)
In-Reply-To: <1168609517.2789.47.camel@garfield.inria.fr>
On Fri, Jan 12, 2007 at 02:45:16PM +0100, Mathieu Lacage wrote:
> Am I right in assuming that the gdb command "break" places exclusively
> so-called software-breakpoints while the command "hbreak" places a
> hardware-breakpoint (I am not sure I have figured out the details of the
> logic in gdb/breakpoint.c) ?
Not 100%. CVS versions of GDB will use hardware breakpoints
automatically if you try to set them in truly read-only memory.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-12 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 11:42 placing a breakpoint at a physical address on x86 with gdb Mathieu Lacage
2007-01-12 12:48 ` Mathieu Lacage
2007-01-12 13:46 ` help string for "break" command Mathieu Lacage
2007-01-12 13:49 ` Daniel Jacobowitz [this message]
2007-01-12 14:20 ` Mathieu Lacage
2007-01-12 14:26 ` Daniel Jacobowitz
2007-01-12 14:27 ` Bob Rossi
2007-01-12 14:34 ` Mathieu Lacage
2007-01-12 18:11 ` mathieu lacage
2007-01-12 23:26 ` 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=20070112134932.GA21726@nevyn.them.org \
--to=drow@false.org \
--cc=Mathieu.Lacage@sophia.inria.fr \
--cc=gdb@sourceware.org \
/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