From: Michael Snyder <msnyder@vmware.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] gdb.base -- use gdb_test_no_output
Date: Fri, 11 Jun 2010 20:57:00 -0000 [thread overview]
Message-ID: <4C12A31B.2060500@vmware.com> (raw)
In-Reply-To: <201006111935.o5BJZ0cJ021385@d12av02.megacenter.de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
Ulrich Weigand wrote:
> Jan Kratochvil wrote:
>
>> FYI in the testcase the inferior is no loner running when `set language asm' is
>> entered. There is preceding:
>>
>> (gdb) run^M
>> Starting program: .../gdb.base/setshow foo bar blup baz bubble^M
>> foo bar blup baz bubble ^M
>> Program exited normally.^M
>> (gdb) PASS: gdb.base/setshow.exp: passing args
>
> Ah, that would explain it! This part of setshow.exp:
>
> # Don't test if we can't pass args or if we're using a stub.
> if { ![target_info exists use_gdb_stub] && ![target_info exists noargs] } {
> #test passing args
> gdb_test "cont" "Continuing.*" "continuing"
> delete_breakpoints
> gdb_test "run" "Starting program:.*foo bar blup baz bubble.*" "passing args"
> }
>
> is skipped on spu-elf because we cannot pass command line arguments
> (well, at least it's not set up that way).
>
> However, it seems to me that this is still a bug: I don't really think the
> intention was that the remaining checks are to be executed on a running
> inferior on some targets, and on a exited inferior on others ...
I'm reverting that line of change, as attached.
[-- Attachment #2: setshow.txt --]
[-- Type: text/plain, Size: 963 bytes --]
2010-06-11 Michael Snyder <msnyder@vmware.com>
* gdb.base/setshow.exp (set language asm): Don't use
gdb_test_no_output, fails on some targets.
Index: gdb.base/setshow.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/setshow.exp,v
retrieving revision 1.18
diff -u -p -r1.18 setshow.exp
--- gdb.base/setshow.exp 10 Jun 2010 19:48:19 -0000 1.18
+++ gdb.base/setshow.exp 11 Jun 2010 20:55:26 -0000
@@ -173,7 +173,7 @@ gdb_test_no_output "set history size 100
#test show history size 100
gdb_test "show history size" "The size of the command history is 100..*" "show history size (100)"
#test set language asm
-gdb_test_no_output "set language asm" "set language asm"
+gdb_test "set language asm" ".*" "set language asm"
#test show language asm
gdb_test "show language" "The current source language is \"asm\"..*" "show language (asm)"
#test set language java, with a trailing space
prev parent reply other threads:[~2010-06-11 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 21:13 Michael Snyder
2010-06-01 19:43 ` Joel Brobecker
2010-06-01 21:30 ` Michael Snyder
2010-06-11 16:31 ` Ulrich Weigand
2010-06-11 17:15 ` Michael Snyder
2010-06-11 18:01 ` Ulrich Weigand
2010-06-11 18:14 ` Ulrich Weigand
2010-06-11 18:27 ` Michael Snyder
2010-06-11 19:05 ` Ulrich Weigand
2010-06-11 19:26 ` Jan Kratochvil
2010-06-11 19:35 ` Ulrich Weigand
2010-06-11 20:57 ` Michael Snyder [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=4C12A31B.2060500@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=uweigand@de.ibm.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