public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, bauerman@br.ibm.com
Subject: Re: [RFA/NEWS] Re: PR corefile/8210: Linux core files should use linux-thread-db.c
Date: Thu, 26 Aug 2010 19:34:00 -0000	[thread overview]
Message-ID: <83fwy1maj7.fsf@gnu.org> (raw)
In-Reply-To: <201008262013.28049.pedro@codesourcery.com>

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Thu, 26 Aug 2010 20:13:27 +0100
> Cc: Thiago Jung Bauermann <bauerman@br.ibm.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.

It's okay, with two comments:

> +* GDB now displays pthread_t ids and allows inspecting TLS variables
> +  when debugging core dumps on GNU/Linux.

Suggest to make a shorter header:

  * GDB now supports thread debugging of core dumps on GNU/Linux.

> +  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

  When debugging a core dump generated on a machine other than the one
  used to run GDB, you may need ...

Thanks.

  reply	other threads:[~2010-08-26 19:34 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       ` [RFA/NEWS] " Pedro Alves
2010-08-26 19:34         ` Eli Zaretskii [this message]
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=83fwy1maj7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).