From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-151060-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 55971 invoked by alias); 20 Sep 2018 04:38:15 -0000
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
Received: (qmail 55960 invoked by uid 89); 20 Sep 2018 04:38:14 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:790
X-HELO: mail-wr1-f66.google.com
Received: from mail-wr1-f66.google.com (HELO mail-wr1-f66.google.com) (209.85.221.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 20 Sep 2018 04:38:13 +0000
Received: by mail-wr1-f66.google.com with SMTP id v16-v6so7869476wro.11        for <gdb-patches@sourceware.org>; Wed, 19 Sep 2018 21:38:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:in-reply-to:references:from:date:message-id:subject:to         :cc;        bh=FZRM0Y7ZS89W/vLnYRK8ptk1NWNRfrdH4R74nzwt/PI=;        b=Oz/0+ElYUXhtp8iOPNZCwJqjaYtU/3oXXRnfn3eBtQVrEal195waHadJ645QTLFeA3         GUs2v14lQI7UxmrYntCl8P3KnmmhSOst+OZm7tD+iRdTkIrbkWCX8sUZFdIe6mgKpWRK         8xuFsf5ajc+KS/9K6Kdm1r+6r936Pqk8H/a3z0LUNtahaitEcZW3cWvZ7QCJkdH9yYbI         8vF+qJLNA89UzjTmji5Ed0K/WjLkEMK2J+YMGVpxfHcvM75e6hgUs8LEvFEjvIwzFyjF         cUFzeyT34Luxhj19lpvG+zKQcW4Kkl+ADBm+dHvDVDn6e7givU0zIYpQjMnUPfmjaMkE         EAiw==
MIME-Version: 1.0
Received: by 2002:adf:8463:0:0:0:0:0 with HTTP; Wed, 19 Sep 2018 21:38:10 -0700 (PDT)
In-Reply-To: <d8e04cee-b1bb-1c2f-b4a2-6262adcc9890@redhat.com>
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>
From: Rajendra SY <rajendra.sy@gmail.com>
Date: Thu, 20 Sep 2018 04:38:00 -0000
Message-ID: <CAMAnt0mVGZR-S0zUZekW69y=mpqgN81BJvzz+jrqXPbispJsnQ@mail.gmail.com>
Subject: Re: [PATCH] [PR 23660] On FreeBSD platform missing implementation of thread-db support
To: Pedro Alves <palves@redhat.com>
Cc: John Baldwin <jhb@freebsd.org>, gdb-patches@sourceware.org
Content-Type: text/plain; charset="UTF-8"
X-SW-Source: 2018-09/txt/msg00725.txt.bz2

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