This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] [PR 23660] On FreeBSD platform missing implementation of thread-db support
- From: Rajendra SY <rajendra dot sy at gmail dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: John Baldwin <jhb at freebsd dot org>, gdb-patches at sourceware dot org
- Date: Thu, 20 Sep 2018 10:08:10 +0530
- Subject: Re: [PATCH] [PR 23660] On FreeBSD platform missing implementation of thread-db support
- References: <CAMAnt0=fYErrp--45kinNV1yx-FxP1hnqOCC_kuMt79vES5ROA@mail.gmail.com> <8b47dccf-0b34-9803-8417-42841dd924a7@FreeBSD.org> <CAMAnt0mHKNfZRcj+XHW+ft0=gd-49Ym-Lyf1rGK5B-foJYsr8A@mail.gmail.com> <d8e04cee-b1bb-1c2f-b4a2-6262adcc9890@redhat.com>
Pedro,
I'll clean up the glibc workaround code.
Thanks
Regards,
Rajendra
On Wed, Sep 19, 2018 at 10:29 PM, Pedro Alves <palves@redhat.com> wrote:
> On 09/19/2018 05:52 PM, Rajendra SY wrote:
>> + /* True if we need to apply the workaround for glibc/BZ5983. When
>> + we catch a PTRACE_O_TRACEFORK, and go query the child's thread
>> + list, nptl_db returns the parent's threads in addition to the new
>> + (single) child thread. If this flag is set, we do extra work to
>> + be able to ignore such stale entries. */
>> + int need_stale_parent_threads_check;
>
> Surely FreeBSD doesn't need a workaround for a glibc bug.
>
> There are other references to glibc in the file.
>
> Thanks,
> Pedro Alves