From: Andrew STUBBS <andrew.stubbs@st.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Enhance break command help
Date: Thu, 01 Dec 2005 12:28:00 -0000 [thread overview]
Message-ID: <438EEBC5.8040802@st.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
Hi,
The attached patch adds more information to the on-line help for the
break command. It adds a brief description how to set thread specific
and conditional breakpoints.
The information is all in the user guide, but was missing from the
internal help message.
This is in response to a complaint from a user.
Thanks
Andrew Stubbs
[-- Attachment #2: break-help.patch --]
[-- Type: text/plain, Size: 1569 bytes --]
2005-12-01 Andrew Stubbs <andrew.stubbs@st.com>
* breakpoint.c (_initialize_breakpoint): Enhance break command help.
Index: src/gdb/breakpoint.c
===================================================================
--- src.orig/gdb/breakpoint.c 2005-12-01 12:05:59.000000000 +0000
+++ src/gdb/breakpoint.c 2005-12-01 12:19:28.000000000 +0000
@@ -7809,13 +7809,17 @@ See also the \"delete\" command which cl
c = add_com ("break", class_breakpoint, break_command, _("\
Set breakpoint at specified line or function.\n\
-Argument may be line number, function name, or \"*\" and an address.\n\
-If line number is specified, break at start of code for that line.\n\
-If function is specified, break at start of code for that function.\n\
+break [LOCATION] [thread THREADNUM] [if CONDITION]\n\
+The LOCATION may be a line number, function name, or \"*\" and an address.\n\
+If a line number is specified, break at start of code for that line.\n\
+If a function is specified, break at start of code for that function.\n\
If an address is specified, break at that exact address.\n\
-With no arg, uses current execution address of selected stack frame.\n\
+With no LOCATION, uses current execution address of selected stack frame.\n\
This is useful for breaking on return to a stack frame.\n\
\n\
+The THREADNUM is the number from \"info threads\".\n\
+The CONDITION is a boolean expression.\n\
+\n\
Multiple breakpoints at one place are permitted, and useful if conditional.\n\
\n\
Do \"help breakpoints\" for info on other commands dealing with breakpoints."));
next reply other threads:[~2005-12-01 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 12:28 Andrew STUBBS [this message]
2005-12-01 16:57 ` Andrew STUBBS
2005-12-02 8:14 ` Eli Zaretskii
2005-12-02 13:54 ` Andrew STUBBS
2005-12-02 14:59 ` Eli Zaretskii
2005-12-02 17:30 ` Andrew STUBBS
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=438EEBC5.8040802@st.com \
--to=andrew.stubbs@st.com \
--cc=gdb-patches@sources.redhat.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