This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Testsuite FAIL which isn't a FAIL in chng-syms.exp
- From: Corinna Vinschen <vinschen at redhat dot com>
- To: gdb at sources dot redhat dot com
- Date: Thu, 26 Feb 2004 17:15:43 +0100
- Subject: Testsuite FAIL which isn't a FAIL in chng-syms.exp
- Reply-to: gdb at sources dot redhat dot com
Hi,
I'm looking for a good while into this testsuite FAIL. What happens
is, that the testsuite generates a FAIL which is not correct. The
expression in chng-syms.exp is this:
gdb_run_cmd
gdb_expect {
-re "Error in re-setting .*No symbol .var1..*Program exited normally.*" {
pass "running with invalidated bpt condition after executable changes"
}
timeout {
fail "(timeout) running with invalidated bpt condition after executable changes"
}
The output from the gdb.log file looks like this:
`/build/sh-elf/gdb/testsuite/gdb.base/chng-syms' has changed; re-reading symbols.^M
Error in re-setting breakpoint 1:^M
No symbol "var1" in current context.^M
Starting program: /build/sh-elf/gdb/testsuite/gdb.base/chng-syms ^M
^M
Program exited normally.^M
(gdb) FAIL: gdb.base/chng-syms.exp: (timeout) running with invalidated bpt condition after executable changes
Does anybody understand why that's failing? The regular expression
looks right to me. I tried to change it to get it working but everything
I tried failed, except for ".*Program exited normally.*" which is not
exactly helpful. :-(
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.