From: Mathieu Lacage <Mathieu.Lacage@sophia.inria.fr>
To: gdb@sourceware.org
Subject: help string for "break" command
Date: Fri, 12 Jan 2007 13:46:00 -0000 [thread overview]
Message-ID: <1168609517.2789.47.camel@garfield.inria.fr> (raw)
In-Reply-To: <1168606081.2789.38.camel@garfield.inria.fr>
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
hi,
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) ?
If so, maybe the gdb help should be updated to reflect this difference
more prominently: the current help string for "break" do not specify
clearly that it is a software-breakpoint. The attached patch changes the
relevant string.
regards,
Mathieu
--
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 455 bytes --]
--- breakpoint.old 2007-01-12 14:38:50.000000000 +0100
+++ breakpoint.c 2007-01-12 14:39:32.000000000 +0100
@@ -7928,7 +7928,7 @@
See also the \"delete\" command which clears breakpoints by number."));
c = add_com ("break", class_breakpoint, break_command, _("\
-Set breakpoint at specified line or function.\n"
+Set software breakpoint at specified line or function.\n"
BREAK_ARGS_HELP ("break")));
set_cmd_completer (c, location_completer);
next prev parent reply other threads:[~2007-01-12 13:46 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 ` Mathieu Lacage [this message]
2007-01-12 13:49 ` help string for "break" command Daniel Jacobowitz
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=1168609517.2789.47.camel@garfield.inria.fr \
--to=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