[Bug go/114581] New: go.test/test/fixedbugs/issue22881.go FAILs

[Bug go/114581] New: go.test/test/fixedbugs/issue22881.go FAILs

[ro at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114581

            Bug ID: 114581
           Summary: go.test/test/fixedbugs/issue22881.go FAILs
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: go
          Assignee: ian at airs dot com
          Reporter: ro at gcc dot gnu.org
  Target Milestone: ---
            Target: sparc-sun-solaris2.11

The go.test/test/fixedbugs/issue22881.go test FAILs on 32-bit Solaris/SPARC
since it was added:

FAIL: go.test/test/fixedbugs/issue22881.go execution,  -O2 -g 

failed to rethrow unwind exception (reason=5)
SIGABRT: abort
PC=0xfd799dc4 m=0 sigcode=4294967295

goroutine 1 [running]:
__lwp_sigqueue
        :0

Weirdly, the test FAILs differently when run under gdb:

hread 6 received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1 (LWP 1)]
main.f0 (m=0x9120a0)
    at
/vol/gcc/src/hg/master/local/gcc/testsuite/go.test/test/fixedbugs/issue22881.go:51
51              m[0] = *p
(gdb) p p
$1 = (int *) 0x0
(gdb) bt
#0  main.f0 (m=0x9120a0)
    at
/vol/gcc/src/hg/master/local/gcc/testsuite/go.test/test/fixedbugs/issue22881.go:51
#1  0x0001470c in main.main..func1 ()
    at
/vol/gcc/src/hg/master/local/gcc/testsuite/go.test/test/fixedbugs/issue22881.go:23
#2  0x00014d5c in main.main ()
    at
/vol/gcc/src/hg/master/local/gcc/testsuite/go.test/test/fixedbugs/issue22881.go:19
(gdb) cont
Continuing.
SIGSEGV: segmentation violation
PC=0x14454 m=0 sigcode=0

goroutine 1 [running]:
main.f0
       
/vol/gcc/src/hg/master/local/gcc/testsuite/go.test/test/fixedbugs/issue22881.go:51
main.main..func1
       
/vol/gcc/src/hg/master/local/gcc/testsuite/go.test/test/fixedbugs/issue22881.go:23
main.main
       
/vol/gcc/src/hg/master/local/gcc/testsuite/go.test/test/fixedbugs/issue22881.go:19

The 64-bit test is fine, however.

[Bug go/114581] go.test/test/fixedbugs/issue22881.go FAILs

[ian at airs dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114581

--- Comment #1 from Ian Lance Taylor <ian at airs dot com> ---
The behavior is different under gdb because gdb resends the signal.  The
program then sees it with an si_code field of SI_USER, which causes it to act
differently.

[Bug go/114581] go.test/test/fixedbugs/issue22881.go FAILs

[ian at airs dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114581

Ian Lance Taylor <ian at airs dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #2 from Ian Lance Taylor <ian at airs dot com> ---
I wrote a long explanation of the problem in PR 114582, so closing this one in
favor of that one.

*** This bug has been marked as a duplicate of bug 114582 ***