* [PATCH][COMMITTED] scm-error.exp: Handle guile 2.2 backtrace output
@ 2014-09-09 5:23 Doug Evans
0 siblings, 0 replies; only message in thread
From: Doug Evans @ 2014-09-09 5:23 UTC (permalink / raw)
To: gdb-patches
Hi.
Testing with recent guile had a failure in scm-error.exp.
Backtraces don't necessarily include parameter values
and can instead be printed as just "_".
2014-09-09 Doug Evans <xdje42@gmail.com>
* gdb.guile/scm-error.exp: Handle guile 2.2 backtrace output.
diff --git a/gdb/testsuite/gdb.guile/scm-error.exp b/gdb/testsuite/gdb.guile/scm-error.exp
index b5a1028..3de3dc2 100644
--- a/gdb/testsuite/gdb.guile/scm-error.exp
+++ b/gdb/testsuite/gdb.guile/scm-error.exp
@@ -95,7 +95,7 @@ gdb_test_no_output "set guile print-stack full" \
"set print-stack to full, for backtrace test"
gdb_test "guile (define x (top-func 42))" \
- "Guile Backtrace:.*top-func 42.*middle-func 42.*bottom-func 42.*" \
+ "Guile Backtrace:.*top-func (42|_).*middle-func (42|_).*bottom-func (42|_).*" \
"backtrace printed"
# Verify gdb-specific errors are printed properly.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-09-09 5:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-09-09 5:23 [PATCH][COMMITTED] scm-error.exp: Handle guile 2.2 backtrace output Doug Evans
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).