gdb.python/py-prompt.exp: restore GDBFLAGS
Commit Message
On 01/12/2015 05:00 PM, Pedro Alves wrote:
> On 01/12/2015 04:55 PM, Sergio Durigan Junior wrote:
>
>> Running the testcase alone seems to be fine. The problem happens when
>> you run the entire gdb.python/ directory:
>>
>> make check RUNTESTFLAGS="--target_board=native-gdbserver --directory=gdb.python"
>
> Ah, yes. I see the bug. Will push a fix in a bit.
Pushed now. Thanks!
-----
Subject: [PATCH] gdb.python/py-prompt.exp: restore GDBFLAGS
The previous change to py-prompt.exp made it return without restoring
GDBFLAGS, resulting in breaking the following tests:
$ make check RUNTESTFLAGS="--target_board=native-gdbserver --directory=gdb.python"
...
Running src/gdb/testsuite/gdb.python/py-prompt.exp ...
Running src/gdb/testsuite/gdb.python/py-section-script.exp ...
ERROR: (timeout) GDB never initialized after 10 seconds.
ERROR: no fileid for gdbuild
ERROR: Couldn't send python print ('test') to GDB.
ERROR: no fileid for gdbuild
ERROR: Couldn't send python print (sys.version_info[0]) to GDB.
ERROR: no fileid for gdbuild
ERROR: Couldn't send python print (sys.version_info[1]) to GDB.
ERROR: no fileid for gdbuild
ERROR: no fileid for gdbuild
...
gdb/testsuite/
2015-01-12 Pedro Alves <palves@redhat.com>
* gdb.python/py-prompt.exp: When the board can't spawn for attach,
restore GDBFLAGS before returning.
---
gdb/testsuite/ChangeLog | 5 +++++
gdb/testsuite/gdb.python/py-prompt.exp | 1 +
2 files changed, 6 insertions(+)
@@ -1,3 +1,8 @@
+2015-01-12 Pedro Alves <palves@redhat.com>
+
+ * gdb.python/py-prompt.exp: When the board can't spawn for attach,
+ restore GDBFLAGS before returning.
+
2015-01-12 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.python/py-frame.exp (test Frame.read_register(rip)): Use
@@ -76,6 +76,7 @@ gdb_test "python print (\"'\" + str(p\[0\]) + \"'\")" "'$gdb_prompt_fail '" \
gdb_exit
if {![can_spawn_for_attach]} {
+ set GDBFLAGS $saved_gdbflags
return 0
}