This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hello, I started realizing yesterday that, once in a while, print_pc.exp fails. It never failed when I ran the testcase separately, but otherwise fails occasionally when I run the entire testsuite. Looking more closely, I think this is because I didn't "swallow" the output from the call to "gdb_start_cmd", and by failing to do so, I created the potential for unsynchronizing command and output (a gdb_test command ends up checking the output from the previous command). Fixed thusly: 2008-01-08 Joel Brobecker <brobecker@adacore.com> * gdb.ada/print_pc.exp: Add verification of where gdb_start_cmd landed. Should also fix random failures in the test following it. Tested on x86-linux. Checked in. -- Joel
Attachment:
print_pc.diff
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |