From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Kevin Pouget <kevin.pouget@gmail.com>,
Tom Tromey <tromey@redhat.com>
Subject: Re: [patch] gdb.python/py-events.exp: Disable multi-inferior for gdbserver [Re: Regression (or a new FAIL?): gdb.python/py-events.exp]
Date: Wed, 26 Oct 2011 15:07:00 -0000 [thread overview]
Message-ID: <201110261448.58804.pedro@codesourcery.com> (raw)
In-Reply-To: <20111009181654.GA4629@host1.jankratochvil.net>
On Sunday 09 October 2011 19:16:54, Jan Kratochvil wrote:
> On Wed, 05 Oct 2011 16:55:28 +0200, Kevin Pouget wrote:
> > what do you want me to do with that, certainly fill a bug report,
> > shall I change anything in my patch?
>
> I realized gdbserver supports multi-inferior by attaching each new inferior
> but it does not yet support (=remote.c ignores) `set detach-on-fork off' at
> all.
Right, there's no support for following forks or execs in the RSP yet.
> Therefore proposing the patch below. I will check it in in some time.
> gdb/testsuite/
> 2011-10-09 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.python/py-events.exp: New comment for `set detach-on-fork off'.
> (inferior 2, Inferior 2 terminated.): Run them only if not remote.
>
> --- a/gdb/testsuite/gdb.python/py-events.exp
> +++ b/gdb/testsuite/gdb.python/py-events.exp
> @@ -53,6 +53,7 @@ gdb_breakpoint "main" {temporary}
>
> gdb_test "run" ".*event type: new_objfile.*new objfile name.*" "New objfile notification"
"run" doesn't work with "target remote" either. If that is succeeding,
it's because it's actually running the default native target,
which is obviously bogus. If that can't be fixed easily, we should skip
the test on remote targets. But if you see failures related to fork
afterwards, maybe that because you have a customboard file that runs
in extended-remote?
>
> +# Ignored for [is_remote target].
> gdb_test_no_output "set detach-on-fork off" ""
>
> gdb_test "Test_Events" "Event testers registered."
> @@ -75,8 +76,10 @@ gdb_test "continue" ".*event type: continue.*
> .*exit code: 12.*
> .*exit inf: 1.*" "Inferior 1 terminated."
>
> -gdb_test "inferior 2" ".*Switching to inferior 2.*"
> -gdb_test "continue" ".*event type: continue.*
> +if ![is_remote target] {
> + gdb_test "inferior 2" ".*Switching to inferior 2.*"
> + gdb_test "continue" ".*event type: continue.*
> .*event type: exit.*
> .*exit code: 12.*
> .*exit inf: 2.*" "Inferior 2 terminated."
> +}
>
--
Pedro Alves
next prev parent reply other threads:[~2011-10-26 13:49 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 9:19 [PATCH] PR/12691 Add the inferior to Python exited event Kevin Pouget
2011-04-21 10:01 ` Eli Zaretskii
2011-04-25 18:19 ` Tom Tromey
2011-04-26 8:24 ` Kevin Pouget
2011-08-31 14:34 ` Kevin Pouget
2011-08-31 14:46 ` Eli Zaretskii
2011-08-31 14:58 ` Kevin Pouget
2011-08-31 17:27 ` Eli Zaretskii
2011-08-31 17:53 ` Tom Tromey
2011-08-31 17:59 ` Eli Zaretskii
2011-09-01 9:18 ` Kevin Pouget
2011-09-01 8:45 ` Kevin Pouget
2011-09-01 10:12 ` Eli Zaretskii
2011-09-01 11:29 ` Kevin Pouget
2011-09-15 12:49 ` Kevin Pouget
2011-09-15 13:58 ` Eli Zaretskii
2011-09-15 14:19 ` Paul_Koning
2011-09-15 15:27 ` Kevin Pouget
2011-09-15 15:42 ` Eli Zaretskii
2011-08-31 15:50 ` Tom Tromey
2011-09-19 10:37 ` Kevin Pouget
2011-09-19 10:41 ` Eli Zaretskii
2011-10-03 16:38 ` Tom Tromey
2011-10-04 8:05 ` Kevin Pouget
2011-10-05 12:15 ` Regression (or a new FAIL?): gdb.python/py-events.exp [Re: [PATCH] PR/12691 Add the inferior to Python exited event] Jan Kratochvil
2011-10-05 12:37 ` Kevin Pouget
2011-10-05 14:16 ` Jan Kratochvil
2011-10-05 14:56 ` Kevin Pouget
2011-10-09 18:17 ` [patch] gdb.python/py-events.exp: Disable multi-inferior for gdbserver [Re: Regression (or a new FAIL?): gdb.python/py-events.exp] Jan Kratochvil
2011-10-26 15:07 ` Pedro Alves [this message]
2011-10-27 10:31 ` [patch] Forbid "run" etc. for use_gdb_stub targets [Re: [patch] gdb.python/py-events.exp: Disable multi-inferior for gdbserver] Jan Kratochvil
2011-10-27 18:26 ` Pedro Alves
2011-10-28 17:40 ` [commit test fixes] " Jan Kratochvil
2011-10-28 17:42 ` Jan Kratochvil
2011-10-28 18:32 ` Pedro Alves
2011-10-29 19:55 ` Jan Kratochvil
2011-12-03 18:37 ` ping: Re: [patch] Forbid "run" etc. for use_gdb_stub targets Jan Kratochvil
2011-12-03 19:15 ` Pedro Alves
2011-12-03 20:22 ` [commit] " Jan Kratochvil
2011-12-04 1:02 ` ping: " Doug Evans
2011-12-04 1:30 ` Jan Kratochvil
2011-12-04 2:55 ` Doug Evans
2011-12-05 20:25 ` Jan Kratochvil
2011-12-05 21:44 ` Doug Evans
2011-12-05 23:36 ` Doug Evans
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=201110261448.58804.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=kevin.pouget@gmail.com \
--cc=tromey@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