From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb.threads/attach-into-signal.exp: don't rely on linux native target's internal debug output
Date: Mon, 20 Feb 2012 12:32:00 -0000 [thread overview]
Message-ID: <4F423BBC.10007@redhat.com> (raw)
In-Reply-To: <20120220085704.GA4966@host2.jankratochvil.net>
On 02/20/2012 08:57 AM, Jan Kratochvil wrote:
> On Fri, 17 Feb 2012 20:37:50 +0100, Pedro Alves wrote:
>> > We can't use this method for the non-threaded case too, because the Linux
>> > native target when attaching finds another signal other than SIGSTOP, puts
>> > that other signal pending, and waits for the SIGSTOP, so siginfo.si_signo
>> > will always show SIGSTOP.
> It works with this patch from Fedora but it is not yet upstreamed:
> ping: [patch 3/4]#3 linux-nat: Do not respawn signals
> http://sourceware.org/ml/gdb-patches/2011-05/msg00407.html
Yeah. We can revisit/simplify the test once that's in.
>> > Jan, is this okay with you?
> Yes.
Great.
>
>
>> > + set test2 "pull thread list"
>> > + gdb_test_multiple "info threads" $test2 {
>> > + -re "\r\n$gdb_prompt $" {
>> > + }
>> > + }
> This can be just:
> gdb_test "info threads" ".*" "pull thread list"
I avoided that on purpose, because that'd generate a PASS for every
attempt/iteration at trying to catch the signal.
> Still this is a bug of extended gdbserver mode.
Yeah, it could be considered a bug. Not only of extended gdbserver
tough. It happens with all remote targets, and we have similar things
in other tests. One thing at a time though, otherwise, I'll never be
done. :-)
Thanks!
--
Pedro Alves
next prev parent reply other threads:[~2012-02-20 12:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 19:37 [PATCH 0/2] gdb.threads/attach-into-signal.exp: prepare for gdbserver Pedro Alves
2012-02-17 19:38 ` [PATCH 1/2] gdb.threads/attach-into-signal.exp: cleanup Pedro Alves
2012-02-17 20:55 ` Tom Tromey
2012-02-17 21:00 ` Pedro Alves
2012-02-17 22:04 ` Tom Tromey
2012-02-20 13:27 ` Pedro Alves
2012-02-21 16:05 ` testsuite: prefix handling Pedro Alves
2012-02-21 18:18 ` Jan Kratochvil
2012-02-21 19:28 ` Pedro Alves
2012-02-21 19:54 ` Tom Tromey
2012-02-21 19:17 ` Tom Tromey
2012-02-21 20:08 ` Pedro Alves
2012-02-21 20:59 ` Pedro Alves
2012-02-21 21:02 ` Tom Tromey
2012-02-21 22:08 ` Pedro Alves
2012-02-21 21:00 ` Tom Tromey
2012-02-21 22:03 ` Pedro Alves
2012-02-17 21:31 ` [PATCH 1/2] gdb.threads/attach-into-signal.exp: cleanup Pedro Alves
2012-03-01 11:47 ` Pedro Alves
2012-02-17 23:55 ` Joel Brobecker
2012-02-20 8:57 ` Jan Kratochvil
2012-02-17 19:52 ` [PATCH 2/2] gdb.threads/attach-into-signal.exp: don't rely on linux native target's internal debug output Pedro Alves
2012-02-20 9:41 ` Jan Kratochvil
2012-02-20 12:32 ` Pedro Alves [this message]
2012-02-20 12:34 ` Jan Kratochvil
2012-02-20 12:37 ` Pedro Alves
2012-02-21 18:17 ` Edjunior Barbosa Machado
2012-02-21 19:11 ` Pedro Alves
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=4F423BBC.10007@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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