public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PR corefile/8210: Linux core files should use linux-thread-db.c
Date: Wed, 18 Aug 2010 14:29:00 -0000	[thread overview]
Message-ID: <1282141768.19094.1.camel@hactar> (raw)
In-Reply-To: <201008181328.38872.pedro@codesourcery.com>

On Wed, 2010-08-18 at 13:28 +0100, Pedro Alves wrote:
> On Saturday 14 August 2010 20:05:49, Pedro Alves wrote:
> 
> >         PR corefile/8210
> > 
> >         gdb/
> >         * linux-thread-db.c (add_thread_db_info): Skip glibc/BZ5983
> >         workaround on core files.
> >         (try_thread_db_load_1): Don't try enabling thread event reporting
> >         on core files.
> >         (thread_db_load): Allow thread_db on core files.
> >         (attach_thread): Don't check thread signals on core files, nor try
> >         really attaching to the thread, nor enabling thread event event
> >         reporting.
> >         (thread_db_detach): Don't try disabing thread event reporting or
> >         removing thread event breakpoints when debugging a core file.
> >         (find_new_threads_callback): Don't try enabling thread event
> >         reporting on core files.
> >         (thread_db_find_new_threads_2): Don't look for a stopped lwp when
> >         debugging a core file.
> >         (thread_db_find_new_threads): Don't update thread
> >         cores (processors) when debugging a core (dump).
> 
> I've applied this as well.

This is patch is great. IMHO it deserves a NEWS entry. :-)
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center

  reply	other threads:[~2010-08-18 14:29 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 [this message]
2010-08-18 14:40     ` Pedro Alves
2010-08-26 19:13       ` [RFA/NEWS] " Pedro Alves
2010-08-26 19:34         ` 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=1282141768.19094.1.camel@hactar \
    --to=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).