This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[obv] testsuite: gdb_breakpoint: catch GDB internal error
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: gdb-patches at sourceware dot org
- Date: Wed, 13 Apr 2011 22:34:27 +0200
- Subject: [obv] testsuite: gdb_breakpoint: catch GDB internal error
Hi,
this was a part of:
[patch] Fix internal error on some -O2 -g breakpoints
http://sourceware.org/ml/gdb-patches/2010-07/msg00533.html
which is obvious, GDB timed out on it instead.
I am not completely sure about trapping on the final prompt(s) but this code
is already present for other cases in lib/gdb.exp in such case the testfile
gets broken anyway.
Thanks,
Jan
http://sourceware.org/ml/gdb-cvs/2011-04/msg00082.html
--- src/gdb/testsuite/ChangeLog 2011/04/13 18:32:25 1.2663
+++ src/gdb/testsuite/ChangeLog 2011/04/13 20:31:01 1.2664
@@ -1,3 +1,7 @@
+2011-04-13 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ * lib/gdb.exp (gdb_breakpoint): New case for a GDB internal error.
+
2011-04-13 Thiago Jung Bauermann <bauerman@br.ibm.com>
* gdb.base/watchpoint.exp (test_inaccessible_watchpoint): Don't
--- src/gdb/testsuite/lib/gdb.exp 2011/03/25 13:08:11 1.169
+++ src/gdb/testsuite/lib/gdb.exp 2011/04/13 20:31:01 1.170
@@ -377,6 +377,11 @@
send_gdb "$pending_response\n"
exp_continue
}
+ -re "A problem internal to GDB has been detected" {
+ fail "setting breakpoint at $function in runto (GDB internal error)"
+ gdb_internal_error_resync
+ return 0
+ }
-re "$gdb_prompt $" {
if { $no_message == 0 } {
fail "setting breakpoint at $function"