No point in relying on stdio in this test. Simply run to a breakpoint
instead.
gdb/testsuite/ChangeLog:
2015-07-29 Pedro Alves <palves@redhat.com>
* gdb.base/siginfo-addr.c (pass): New function.
(handler): Call it iff si_addr is correct.
* gdb.base/siginfo-addr.exp: Remove gdb_skip_stdio_test check.
Set a breakpoint at "pass" and continue to it.
+2015-07-29 Pedro Alves <palves@redhat.com>
+
+ * gdb.base/siginfo-addr.c (pass): New function.
+ (handler): Call it iff si_addr is correct.
+ * gdb.base/siginfo-addr.exp: Remove gdb_skip_stdio_test check.
+ Set a breakpoint at "pass" and continue to it.
+
2015-07-28 Sergio Durigan Junior <sergiodj@redhat.com>
* gdb.python/py-objfile.exp: Make some tests have unique names.
static void *p;
+void
+pass (void)
+{
+}
+
static void
handler (int sig, siginfo_t *info, void *context)
{
if (info->si_addr == p)
- printf ("Correct si_addr value.\n");
- else
- printf ("Got si_addr = %p, expected %p.\n", info->si_addr, p);
+ pass ();
_exit (0);
}
continue
}
-if [gdb_skip_stdio_test "siginfo-addr.exp"] {
- continue
-}
-
-
standard_testfile
if {[prepare_for_testing $testfile.exp $testfile $srcfile debug]} {
untested "Couldn't compile ${srcfile}.c"
# Run to the signal.
gdb_test "continue" ".*Program received signal SIGSEGV.*" "continue to signal"
+gdb_breakpoint "pass"
+
# Check for correct si_addr.
-set test "program exit"
-gdb_test_multiple "continue" "${test}" {
- -re "Correct si_addr" {
- pass "si_addr value"
- }
- -re "Got si_addr" {
- fail "si_addr value"
- }
-}
+gdb_test "continue" "Breakpoint .* pass .*" "correct si_addr"