From: Pedro Alves <palves@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix PR 12702 - gdb can hang waiting for thread group leader (gdbserver)
Date: Wed, 24 Jul 2013 18:25:00 -0000 [thread overview]
Message-ID: <51F01C13.3080402@redhat.com> (raw)
In-Reply-To: <CANFwon2cWyxzWi+Sqfk6mUK0ZCWQRisMmGWe6mxPMgDLTV_j2g@mail.gmail.com>
On 07/20/2013 10:59 AM, Hui Zhu wrote:
> Hi,
>
> I got a issue with leader-exit.exp will hang with target_board=native-gdbserver.
> I found the reason is gdbserver still have this issue. So I post a
> patch for gdbserver.
leader-exit.exp is part of a series of tests for a set of related
problems. See:
http://www.sourceware.org/ml/gdb-patches/2011-10/msg00704.html
Several are currently masked because gdbserver doesn't support
fork/exec yet.
We should fix this by implementing TARGET_WAITKIND_NO_RESUMED
on gdbserver, like the patch above did for native.
--
Pedro Alves
next prev parent reply other threads:[~2013-07-24 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 10:00 Hui Zhu
2013-07-24 18:25 ` Pedro Alves [this message]
2013-11-19 6:19 ` Hui Zhu
2014-01-23 14:51 ` Pedro Alves
2014-01-23 14:10 ` [PATCH 1/5] Move ptid_match to common/ptid.c Pedro Alves
2014-01-23 14:10 ` [PATCH 2/5] Move status_to_str to nat/linux-waitpid.c Pedro Alves
2014-01-23 14:10 ` [PATCH 3/5] Linux waitpid/__WALL emulation wrapper: If WNOHANG is set, don't touch sigprocmask Pedro Alves
2014-02-27 14:47 ` Pedro Alves
2014-01-23 14:10 ` [PATCH 4/5] Teach gdbserver's linux backend about no unwaited-for children (TARGET_WAITDKIND_NO_RESUMED) Pedro Alves
2014-01-23 14:10 ` [PATCH 5/5] Add TARGET_WAITKIND_NO_RESUMED support to the RSP Pedro Alves
2014-02-27 14:38 ` [PATCH] Fix PR 12702 - gdb can hang waiting for thread group leader (gdbserver) Pedro Alves
2014-02-27 14:54 ` Luis Machado
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=51F01C13.3080402@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@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