From: Pedro Alves <palves@redhat.com>
To: Rajendra SY <rajendra.sy@gmail.com>, John Baldwin <jhb@freebsd.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [PR 23660] On FreeBSD platform missing implementation of thread-db support
Date: Wed, 19 Sep 2018 16:59:00 -0000 [thread overview]
Message-ID: <d8e04cee-b1bb-1c2f-b4a2-6262adcc9890@redhat.com> (raw)
In-Reply-To: <CAMAnt0mHKNfZRcj+XHW+ft0=gd-49Ym-Lyf1rGK5B-foJYsr8A@mail.gmail.com>
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
next prev parent reply other threads:[~2018-09-19 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 13:21 Rajendra SY
2018-09-17 17:11 ` John Baldwin
2018-09-19 16:52 ` Rajendra SY
2018-09-19 16:59 ` Pedro Alves [this message]
2018-09-20 4:38 ` Rajendra SY
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=d8e04cee-b1bb-1c2f-b4a2-6262adcc9890@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=rajendra.sy@gmail.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