This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/65813] GO: bug347.go segment violation on S390x
- From: "ian at airs dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 20 Apr 2015 15:45:45 +0000
- Subject: [Bug go/65813] GO: bug347.go segment violation on S390x
- Auto-submitted: auto-generated
- References: <bug-65813-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65813
--- Comment #1 from Ian Lance Taylor <ian at airs dot com> ---
I think you know this, but to be clear, the test is supposed to dereference a
null pointer, and then it's supposed to recover from the run time panic.
The program should unwind the stack for the signal and call __go_check_defer
which should invoke the deferred function. Can you find out where that process
is going awry?
If the recover* tests pass, then this test ought to pass, or at least it ought
not to fail in this way.