From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Run process-dies-while-detaching.exp with SW watchpoint
Date: Wed, 24 Aug 2016 10:27:00 -0000 [thread overview]
Message-ID: <CAH=s-PN7vcudu1CpRNxLBDo=i+hiOtCPT2gZHUn5qZLiAu==-g@mail.gmail.com> (raw)
In-Reply-To: <2a6bb905-26ad-a496-7fbf-74f99f62a48f@redhat.com>
On Tue, Aug 23, 2016 at 4:20 PM, Pedro Alves <palves@redhat.com> wrote:
>>
>> looks linux-nat target thinks the thread is stopped, but thread-db can't
>> find the thread. Is it a known problem (in gdb or glibc)?
>>
>
> Doesn't this just mean that the process died meanwhile?
> That's the point of the test. /proc/TID/status probably shows
> that the thread is now zombie.
Yes, I know what happened there, but not sure what is the best place
to fix the problem. IIUC, we need to fix GDB somewhere to handle
such case that linux-nat thinks the thread is stopped, but thread-db
can't find it, is it right?
--
Yao (齐尧)
prev parent reply other threads:[~2016-08-24 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 14:47 Yao Qi
2016-08-23 15:21 ` Pedro Alves
2016-08-24 10:27 ` Yao Qi [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='CAH=s-PN7vcudu1CpRNxLBDo=i+hiOtCPT2gZHUn5qZLiAu==-g@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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