From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EBDE73858404; Wed, 29 Dec 2021 00:53:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EBDE73858404 From: "matoro_gcc_bugzilla at matoro dot tk" To: gcc-bugs@gcc.gnu.org Subject: [Bug go/103847] gccgo SIGSEGV in libgo standard library on sparc64 Date: Wed, 29 Dec 2021 00:53:21 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 11.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: matoro_gcc_bugzilla at matoro dot tk X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2021 00:53:22 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103847 --- Comment #5 from matoro --- (In reply to Ian Lance Taylor from comment #4) > There don't seem to be any sparc64-linux machines in the GCC compile farm, > so I can't recreate this myself. >=20 > Are you able to recreate the problem while running under gdb? A backtrace > from the point of the signal might help. The stack backtraces you includ= ed > unfortunately don't tell me anything useful. Thanks. For some reason despite compiling with debug symbols I can't seem to get gd= b to recognize the symbol table, all I get is: $ GOMAXPROCS=3D1 CGO_ENABLED=3D1 GO111MODULE=3Don gdb -q --args /usr/bin/go= -11 build Reading symbols from /usr/bin/go-11... (gdb) r Starting program: /usr/bin/go-11 build [New LWP 51735] [New LWP 51736] Thread 1 "go-11" received signal SIGSEGV, Segmentation fault. 0xfff80001010c11ac in ?? () (gdb) bt full #0 0xfff80001010c11ac in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb)=20 $ file -L /usr/bin/go-11 /usr/bin/go-11: ELF 64-bit MSB pie executable, SPARC V9, relaxed memory ordering, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux.so.2, for GNU/Linux 3.2.0, with debug_info, not stripped $ ldd /usr/bin/go-11 linux-vdso.so.1 (0xfff8000100680000) libgo.so.19 =3D> /usr/lib/gcc/sparc64-unknown-linux-gnu/11.2.1/libgo.so.19 (0xfff80001006840= 00) libm.so.6 =3D> /lib64/libm.so.6 (0xfff80001020c0000) libc.so.6 =3D> /lib64/libc.so.6 (0xfff8000102278000) libgcc_s.so.1 =3D> /usr/lib/gcc/sparc64-unknown-linux-gnu/11.2.1/libgcc_s.so.1 (0xfff8000102508000) /lib64/ld-linux.so.2 (0xfff8000100000000) $ file -L /usr/lib/gcc/sparc64-unknown-linux-gnu/11.2.1/libgo.so.19 /usr/lib/gcc/sparc64-unknown-linux-gnu/11.2.1/libgo.so.19: ELF 64-bit MSB shared object, SPARC V9, relaxed memory ordering, version 1 (SYSV), dynamic= ally linked, with debug_info, not stripped $ readelf -S /usr/bin/go-11 | grep -i "debug" [27] .debug_aranges PROGBITS 0000000000000000 005ad1e6 [28] .debug_info PROGBITS 0000000000000000 005ade86 [29] .debug_abbrev PROGBITS 0000000000000000 0075e02a [30] .debug_line PROGBITS 0000000000000000 00772a5a [31] .debug_frame PROGBITS 0000000000000000 007f5b20 [32] .debug_str PROGBITS 0000000000000000 007f5b70 [33] .debug_line_str PROGBITS 0000000000000000 00846a06 [34] .debug_loclists PROGBITS 0000000000000000 0084adc8 [35] .debug_rnglists PROGBITS 0000000000000000 0094e386 I am able to provide ssh access to the live system on which this is occurri= ng - would that be helpful or is that not really something you prefer to do in t= he course of debugging?=