From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/6] Introduce $inferior_spawn_id, make interrupt.exp work with GDBserver
Date: Tue, 07 Apr 2015 17:31:00 -0000 [thread overview]
Message-ID: <5524145D.8010103@redhat.com> (raw)
In-Reply-To: <1424699660-11727-1-git-send-email-palves@redhat.com>
On 02/23/2015 01:54 PM, Pedro Alves wrote:
> After fixing a gdbserver syscall restart issue, I thought of adding a
> new test to exercise syscall restarting. Then I recalled that we
> already have interrupt.exp for that. However, that test is skipped on
> gdbserver, because it relies on inferior i/o.
>
> When testing with gdbserver, inferior are spawned by gdbserver, on
> gdbserver's pty, and so gdb_test_multiple/gdb_expect, don't see the
> inferior's i/o.
>
> This series introduces a mechanism that allows tests to match inferior
> i/o separately from gdb i/o, like:
>
> send_inferior "echo me\n"
> gdb_test_multiple "continue" "test msg" {
> -i "$inferior_spawn_id" -re "echo me\r\necho\r\n" {
> ...
> }
> -i "$gdb_spawn_id" -re "error.*$gdb_prompt $" {
> ...
> }
> }
>
> and then adjusts interrupt.exp to use the new mechanism.
>
> I took the idea from Don Breazeal's use of $server_spawn_id here
> <https://sourceware.org/ml/gdb-patches/2015-01/msg00689.html>, and
> generalized it.
>
> A couple bugs had to be fixed along the way, and I took the change to
> clean up interrupt.exp to use gdb_test_multiple instead of gdb_expect
> too. interrupt.exp now passes against gdbserver here, on x86_64
> Fedora 20 (It fails with gdbserver/-m32 testing in the exact same way
> it fails on native/-m32 testing, due to a kernel bug).
>
I've now pushed this series in.
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-04-07 17:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 13:54 Pedro Alves
2015-02-23 13:54 ` [PATCH 3/6] gdb_test_multiple: Fix user code argument processing Pedro Alves
2015-02-23 13:54 ` [PATCH 4/6] testsuite: Don't use expect_background to reap gdbserver Pedro Alves
2015-04-13 11:42 ` Yao Qi
2015-04-13 12:09 ` Pedro Alves
2015-04-13 13:25 ` Yao Qi
2015-04-13 13:52 ` Pedro Alves
2015-04-13 14:20 ` Yao Qi
2015-04-13 14:22 ` Pedro Alves
2015-04-13 14:48 ` Yao Qi
2015-02-23 13:54 ` [PATCH 1/6] gdb.base/interrupt.exp: Fix race Pedro Alves
2015-02-23 13:54 ` [PATCH 6/6] gdb.base/interrupt.exp: Use send_inferior/$inferior_spawn_id Pedro Alves
2015-02-23 13:54 ` [PATCH 2/6] gdb.base/interrupt.exp: Use gdb_test_multiple instead of gdb_expect Pedro Alves
2015-02-23 14:28 ` [PATCH 5/6] testsuite: Introduce $inferior_spawn_id Pedro Alves
2015-02-24 16:31 ` Yao Qi
2015-02-27 10:42 ` Pedro Alves
2015-02-27 10:59 ` Pedro Alves
2015-02-27 11:01 ` Pedro Alves
2015-02-27 12:12 ` Yao Qi
2015-02-27 13:59 ` [pushed] Add "../lib/unbuffer_output.c" and use it in gdb.base/interrupt.c (Re: [PATCH 5/6] testsuite: Introduce $inferior_spawn_id) Pedro Alves
2015-02-27 14:13 ` Yao Qi
2015-02-27 14:42 ` Eli Zaretskii
2015-02-27 14:47 ` Pedro Alves
2015-02-27 12:08 ` [PATCH 5/6] testsuite: Introduce $inferior_spawn_id Yao Qi
2015-02-27 12:30 ` Pedro Alves
2015-04-16 16:55 ` Antoine Tremblay
2015-04-16 17:14 ` Pedro Alves
2015-04-21 18:25 ` Pedro Alves
2015-04-21 18:32 ` Antoine Tremblay
2015-04-07 17:31 ` Pedro Alves [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=5524145D.8010103@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
/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