From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>
Subject: [RFA/NEWS] Re: PR corefile/8210: Linux core files should use linux-thread-db.c
Date: Thu, 26 Aug 2010 19:13:00 -0000 [thread overview]
Message-ID: <201008262013.28049.pedro@codesourcery.com> (raw)
In-Reply-To: <201008181540.23064.pedro@codesourcery.com>
On Wednesday 18 August 2010 15:40:22, Pedro Alves wrote:
> On Wednesday 18 August 2010 15:29:28, Thiago Jung Bauermann wrote:
> > This is patch is great. IMHO it deserves a NEWS entry. :-)
>
> Eh eh, I knew that was comming. :-) I'll take care of that a
> bit later.
And here it is. Okay to apply?
--
Pedro Alves
2010-08-26 Pedro Alves <pedro@codesourcery.com>
* NEWS: Mention libthread_db debugging with core files.
---
gdb/NEWS | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
Index: src/gdb/NEWS
===================================================================
--- src.orig/gdb/NEWS 2010-08-26 14:49:39.000000000 +0100
+++ src/gdb/NEWS 2010-08-26 20:12:52.000000000 +0100
@@ -37,6 +37,29 @@
expression. Such a watchpoint is never deleted due to it going out
of scope.
+* GDB now displays pthread_t ids and allows inspecting TLS variables
+ when debugging core dumps on GNU/Linux.
+
+ GDB now activates thread debugging using the libthread_db library
+ when debugging GNU/Linux core dumps, similarly to when debugging
+ live processes. As a result, when debugging a core dump file, GDB
+ now able to display pthread_t ids of threads. For example, "info
+ threads" shows the same output as when debugging the process when it
+ was live. In earlier releases, you'd see something like this:
+
+ (gdb) info threads
+ * 1 LWP 6780 0x00007f0f567be38d main () at main.c:10
+
+ While now you see this:
+
+ (gdb) info threads
+ * 1 Thread 0x7f0f5712a700 (LWP 6780) main () at main.c:10
+
+ When debugging a core dump generated on a machine not the one used
+ to run GDB, you may need to point GDB at the correct libthread_db
+ library with the "set libthread-db-search-path". See the user
+ manual for more details on this command.
+
*** Changes in GDB 7.2
* Shared library support for remote targets by default
next prev parent reply other threads:[~2010-08-26 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 19:06 Pedro Alves
2010-08-18 12:28 ` Pedro Alves
2010-08-18 14:29 ` Thiago Jung Bauermann
2010-08-18 14:40 ` Pedro Alves
2010-08-26 19:13 ` Pedro Alves [this message]
2010-08-26 19:34 ` [RFA/NEWS] " Eli Zaretskii
2010-08-26 19:47 ` Pedro Alves
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=201008262013.28049.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=bauerman@br.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).