From: Michael Snyder <msnyder@specifix.com>
To: gdb-patches@sourceware.org
Subject: [OB] _initialize_infrun, whitespace and typo fix
Date: Tue, 24 Jun 2008 20:07:00 -0000 [thread overview]
Message-ID: <1214335908.3601.1219.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 23 bytes --]
Committed as obvious
[-- Attachment #2: ws.txt --]
[-- Type: text/x-patch, Size: 1691 bytes --]
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.9484
diff -u -p -r1.9484 ChangeLog
--- ChangeLog 24 Jun 2008 02:33:14 -0000 1.9484
+++ ChangeLog 24 Jun 2008 19:29:44 -0000
@@ -1,3 +1,7 @@
+2008-06-24 Michael Snyder <msnyder@specifix.com>
+
+ * infrun.c (_initialize_infrun): White space and typo fix.
+
2008-06-23 Christopher Faylor <me.gdb.changelog@cgf.cx>
* win32-nat.c (safe_symbol_file_add_stub): Remove unused variable.
Index: infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.281
diff -u -p -r1.281 infrun.c
--- infrun.c 13 Jun 2008 20:19:19 -0000 1.281
+++ infrun.c 24 Jun 2008 19:29:45 -0000
@@ -4624,17 +4624,16 @@ function is skipped and the step command
&setlist, &showlist);
add_setshow_boolean_cmd ("can-use-displaced-stepping", class_maintenance,
- &can_use_displaced_stepping, _("\
+ &can_use_displaced_stepping, _("\
Set debugger's willingness to use displaced stepping."), _("\
Show debugger's willingness to use displaced stepping."), _("\
-If zero, gdb will not use to use displaced stepping to step over\n\
+If zero, gdb will not use displaced stepping to step over\n\
breakpoints, even if such is supported by the target."),
- NULL,
- show_can_use_displaced_stepping,
- &maintenance_set_cmdlist,
+ NULL,
+ show_can_use_displaced_stepping,
+ &maintenance_set_cmdlist,
&maintenance_show_cmdlist);
-
/* ptid initializations */
null_ptid = ptid_build (0, 0, 0);
minus_one_ptid = ptid_build (-1, 0, 0);
reply other threads:[~2008-06-24 19:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1214335908.3601.1219.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb-patches@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