Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] GNU/Linux: Stop using libthread_db/td_ta_thr_iter
Date: Fri, 20 Feb 2015 21:46:00 -0000	[thread overview]
Message-ID: <54E7AB2A.1070501@redhat.com> (raw)
In-Reply-To: <1423422659-27559-1-git-send-email-palves@redhat.com>

On 02/08/2015 07:10 PM, Pedro Alves wrote:
> This one made me scratch my head for a while.  My
> all-stop-on-top-of-non-stop series was causing odd GDB hangs.  Turned
> out to be that we can't use libthread_db/td_ta_thr_iter when threads
> are running.  This series stops GDB from using it altogether, when
> debugging live programs.
>
> The second patch is the real deal.  The first patch fixes latent bugs
> that the second patch's test exposed, though after the second patch,
> the buggy function won't be used on modern system anymore...
>
> Pedro Alves (2):
>   linux-nat.c: fix a few lin_lwp_attach_lwp issues
>   GNU/Linux: Stop using libthread_db/td_ta_thr_iter

I've pushed this in now.

Thanks,
Pedro Alves


      parent reply	other threads:[~2015-02-20 21:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 19:11 Pedro Alves
2015-02-08 19:11 ` [PATCH 1/2] linux-nat.c: fix a few lin_lwp_attach_lwp issues Pedro Alves
2015-02-08 19:11 ` [PATCH 2/2] GNU/Linux: Stop using libthread_db/td_ta_thr_iter Pedro Alves
2015-08-26 17:39   ` Cell multi-arch broken (Re: [PATCH 2/2] GNU/Linux: Stop using libthread_db/td_ta_thr_iter) Ulrich Weigand
2015-08-26 18:23     ` Pedro Alves
2015-08-26 19:02       ` Ulrich Weigand
2015-08-26 19:42         ` Pedro Alves
2015-08-27 17:40           ` Ulrich Weigand
2015-08-28  6:21         ` Doug Evans
2015-08-28 13:11           ` Ulrich Weigand
2015-09-08 10:31           ` Pedro Alves
2015-09-19  6:21           ` Doug Evans
2015-02-20 21:46 ` Pedro Alves [this message]

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=54E7AB2A.1070501@redhat.com \
    --to=palves@redhat.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