From: Luis Machado <lgustavo@codesourcery.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Harden gdb.base/coredump-filter.exp
Date: Fri, 10 Apr 2015 13:11:00 -0000 [thread overview]
Message-ID: <5527CBEC.6030002@codesourcery.com> (raw)
In-Reply-To: <86pp7cv23w.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]
On 04/10/2015 05:06 AM, Yao Qi wrote:
> 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?
>
Yes, this is user mode. I suppose a system mode QEMU running gdbserver
would work just fine. I made that information explicit in this updated
version.
>> + # 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.
>
That still gives me one FAIL due to not matching what was expected. Did
you mean a check inside this gdb_test_multiple?
[-- Attachment #2: coredump-filter.diff --]
[-- Type: text/x-patch, Size: 1285 bytes --]
2015-04-10 Luis Machado <lgustavo@codesourcery.com>
gdb/testsuite/
* gdb.base/coredump-filter.exp: Restrict test to Linux systems only.
Handle the case of targets that do not provide PID information.
---
gdb/testsuite/gdb.base/coredump-filter.exp | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/gdb/testsuite/gdb.base/coredump-filter.exp b/gdb/testsuite/gdb.base/coredump-filter.exp
index f3203be..8350981 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 {
+ untested "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,12 @@ 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 usermode QEMU),
+ # just bail out as the rest of the test may rely on it, giving spurious
+ # failures.
+ return -1
+ }
}
# Get the main function's address.
--
1.9.1
next prev parent reply other threads:[~2015-04-10 13:11 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
2015-04-10 13:11 ` Luis Machado [this message]
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=5527CBEC.6030002@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@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