http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59432
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE ro at CeBiTec dot
Uni-Bielefeld.DE ---
--- Comment #1 from Ian Lance Taylor ian at airs dot com ---
FYI, the point of the test is to get that segmentation violation and ensure
that the signal handler generates a runtime panic as it should. The actual
problem is presumably happening some time later.
Thanks for the hint. Investigating further proved a bit difficult:
running with -test.run=TestNilDeref under gdb with SEGV just passed on
ran for hours without anything happening.
Instead, I've run the test with truss -S ABRT (stop on SIGABRT) and got
the following stacktrace from an attached gdb:
#0 0xfe52c955 in _lwp_kill () from /lib/libc.so.1
#1 0xfe5277d9 in thr_kill () from /lib/libc.so.1
#2 0xfe4d3893 in raise () from /lib/libc.so.1
#3 0xfe4b2988 in abort () from /lib/libc.so.1
#4 0xfe8c36a0 in __go_check_defer (frame=frame@entry=0xde836faf) at
/vol/gcc/src/hg/trunk/local/libgo/runtime/go-unwind.c:152
#5 0xfe976e62 in testing.tRunner (test=optimized out, t.param=optimized
out) at /vol/gcc/src/hg/trunk/local/libgo/go/testing/testing.go:392
#6 testing.$thunk13 (__go_thunk_parameter=0xde200688) at
/vol/gcc/src/hg/trunk/local/libgo/go/testing/testing.go:471
#7 0xfe8d005b in kickoff () at
/vol/gcc/src/hg/trunk/local/libgo/runtime/proc.c:229
#8 0xfe4a5ba2 in makecontext () from /lib/libc.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
This might be another instance of problems unwinding through makecontext.
Rainer
