Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: "Gustavo\, Luis" <luis_gustavo@mentor.com>
Cc: "'gdb-patches\@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Harden gdb.base/coredump-filter.exp
Date: Fri, 10 Apr 2015 08:06:00 -0000	[thread overview]
Message-ID: <86pp7cv23w.fsf@gmail.com> (raw)
In-Reply-To: <5526D4A1.9090203@mentor.com> (Luis Gustavo's message of "Thu, 9	Apr 2015 16:36:01 -0300")

Luis Gustavo <luis_gustavo@mentor.com> writes:

> diff --git a/gdb/testsuite/gdb.base/coredump-filter.exp b/gdb/testsuite/gdb.base/coredump-filter.exp
> index f3203be..4c6c6ed 100644
> --- a/gdb/testsuite/gdb.base/coredump-filter.exp
> +++ b/gdb/testsuite/gdb.base/coredump-filter.exp
> @@ -15,6 +15,12 @@
>  
>  standard_testfile
>  
> +# This test is Linux-only.
> +if ![istarget *-*-linux*] then {
> +    unsupported "coredump-filter.exp"
> +    return -1
> +}
> +
>  if { [prepare_for_testing "failed to prepare" $testfile $srcfile debug] } {
>      untested "could not compile test program"
>      return -1
> @@ -146,6 +152,11 @@ gdb_test_multiple "info inferiors" "getting inferior pid" {
>      -re "process \($decimal\).*\r\n$gdb_prompt $" {
>  	set infpid $expect_out(1,string)
>      }
> +    -re "Remote target.*$gdb_prompt $" {
> +	# If the target does not provide PID information (like QEMU), just bail

FAOD, QEMU here is QEMU user mode, isn't?

> +	# out as the rest of the test may rely on it, giving spurious failures.
> +	return -1
> +    }
>  }

We can just bail out if infpid is still "" after this gdb_test_multiple.

-- 
Yao (齐尧)


  reply	other threads:[~2015-04-10  8:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 19:36 Luis Gustavo
2015-04-10  8:06 ` Yao Qi [this message]
2015-04-10 13:11   ` Luis Machado
2015-04-10 15:16     ` Yao Qi
2015-04-13 17:50       ` Luis Machado
2015-04-10  8:45 ` 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=86pp7cv23w.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis_gustavo@mentor.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