From: Michael Snyder <msnyder@vmware.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Eli Zaretskii <eliz@gnu.org>
Subject: [commit] doc/gdb.texinfo: Update example of a linux "New Thread" message
Date: Mon, 14 Feb 2011 23:42:00 -0000 [thread overview]
Message-ID: <4D59B7E2.6070300@vmware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 49 bytes --]
These have changed since this was last updated.
[-- Attachment #2: new.txt --]
[-- Type: text/plain, Size: 623 bytes --]
2011-02-14 Michael Snyder <msnyder@vmware.com>
* gdb.texinfo (Threads): Update example of new thread message.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.798
diff -u -p -u -p -r1.798 gdb.texinfo
--- gdb.texinfo 14 Feb 2011 11:13:11 -0000 1.798
+++ gdb.texinfo 14 Feb 2011 23:13:36 -0000
@@ -2683,7 +2683,7 @@ whose form varies depending on the parti
@sc{gnu}/Linux, you might see
@smallexample
-[New Thread 46912507313328 (LWP 25582)]
+[New Thread 0x41e02940 (LWP 25582)]
@end smallexample
@noindent
next reply other threads:[~2011-02-14 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 23:42 Michael Snyder [this message]
2011-02-15 4:01 ` 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=4D59B7E2.6070300@vmware.com \
--to=msnyder@vmware.com \
--cc=eliz@gnu.org \
--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