public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "mikeowens at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/30430] New: SIGABRT on run (Illumos on SPARC) Date: Mon, 08 May 2023 21:02:17 +0000 [thread overview] Message-ID: <bug-30430-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30430 Bug ID: 30430 Summary: SIGABRT on run (Illumos on SPARC) Product: gdb Version: 13.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: mikeowens at gmail dot com Target Milestone: --- This is specifically a SPARC issue. I am running the latest OpenIndiana on a T4-1. I can provide SSH access to the machine to assist anyone willing to help with this bug. I experience the following problem with every version of gdb I can get: 10.1, 12.1-202, 13.1. No matter how simple the program, the moment I start it to debug I get the same result. Here is a simple case. I use the following program: int main() { return 0; } Compile as follows: g++ -ggdb test.cpp The gcc version is 11.3.0 (OpenIndiana 11.3.0-oi-4) Then I run gdb as follows: # $ gdb a.out Exception caught while booting Guile. Error in function "load-thunk-from-memory": ELF file does not have native word size /usr/local/bin/gdb: warning: Could not complete Guile gdb module initialization from: /usr/local/share/gdb/guile/gdb/boot.scm. Limited Guile support is available. Suggest passing --data-directory=/path/to/gdb/data-directory. GNU gdb (GDB) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.11". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /var/data/tmp/a.out... (gdb) run Starting program: /tmp/a.out [Thread debugging using libthread_db enabled] Fatal signal: Abort ----- Backtrace ----- Abort (core dumped) If I run mbd on the core file I get no useful information: # mdb core Loading modules: [ libc.so.1 ld.so.1 ] > $C mdb: failed to get current register set: invalid thread identifier When I run truss I see the following: /1: open("/lib/64/libc.so.1", O_RDONLY) = 18 /1: fcntl(18, F_GETFD, 0x00000000) = 0 /1: fcntl(18, F_SETFD, 0x00000001) = 0 /1: lseek(18, 1467912, SEEK_SET) = 1467912 /1: fstat(18, 0xFFFFFFFF7FFF9760) = 0 /1: fstat(18, 0xFFFFFFFF7FFF9580) = 0 /1: ioctl(18, TCGETA, 0xFFFFFFFF7FFF969E) Err#25 ENOTTY /1: read(18, "7F D O F02020102\b\b\0\0".., 131072) = 131072 /1: open("/var/data/tmp/a.out", O_RDONLY) = 20 /1: fcntl(20, F_GETFD, 0x00000000) = 0 /1: fcntl(20, F_SETFD, 0x00000001) = 0 /1: lseek(20, 4328, SEEK_SET) = 4328 /1: fstat(20, 0xFFFFFFFF7FFF5F70) = 0 /1: fstat(20, 0xFFFFFFFF7FFF5D90) = 0 /1: ioctl(20, TCGETA, 0xFFFFFFFF7FFF5EAE) Err#25 ENOTTY /1: read(20, "\0\0\0\0\0\0\001\0\0\0\0".., 10752) = 6024 /1: lseek(17, 0, SEEK_SET) = 0 /1: read(17, "\t \003\0\0\001\006\003".., 1392) = 1392 /1: lseek(19, 4294967360, SEEK_SET) = 4294967360 /1: read(19, "\0\0\006\0\0\005\0\0\0\0".., 56) = 56 /1: lseek(17, 0, SEEK_SET) = 0 /1: read(17, "\t \003\0\0\001\006\003".., 1392) = 1392 /1: lseek(19, 4294967416, SEEK_SET) = 4294967416 /1: read(19, "\0\0\003\0\0\004\0\0\0\0".., 56) = 56 /1: lseek(17, 0, SEEK_SET) = 0 /1: read(17, "\t \003\0\0\001\006\003".., 1392) = 1392 /1: lseek(19, 4294967472, SEEK_SET) = 4294967472 /1: read(19, "\0\0\001\0\0\005\0\0\0\0".., 56) = 56 /1: lseek(17, 0, SEEK_SET) = 0 ... /1: read(20, "\0\0\0\0\0\0\001\0\0\0\0".., 10752) = 6024 /1: lseek(17, 0, SEEK_SET) = 0 /1: read(17, "\t \003\0\0\001\006\003".., 1392) = 1392 /1: lseek(19, 4296020768, SEEK_SET) = 4296020768 /1: read(19, "FFFFFFFF `84 \0", 8) = 8 /1: sigaction(SIGABRT, 0x00000000, 0xFFFFFFFF7FFF5820) = 0 /1: lwp_kill(1, SIGABRT) = 0 /1: Received signal #6, SIGABRT [caught] /1: siginfo: SIGABRT pid=20069 uid=100 code=-1 /1: lwp_sigmask(SIG_SETMASK, 0x00000000, 0x00000000, 0x00000000, 0x00000000) = 0xFFBFFEFF [0xFFFFFFFF] I get this exact same error on every version of gdb I test with. I understand that SPARC is a dead platform, but thankfully it seems that gdb still has theoretical support for it. The code built cleanly from source. You can still get really good deals on SPARC hardware and I would love to be able to use this system for a long time to come. But without a working debugger, this system is utterly useless. Like I said, I can provide direct access to the machine for anyone willing to work on the issue. It's a great machine with 250GB RAM and 64 cores. It's a lot of fun to work on it. And I have pkgsrc set up on it so I can build any additional tools that might be helpful. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-05-08 21:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-08 21:02 mikeowens at gmail dot com [this message] 2023-05-08 21:20 ` [Bug c++/30430] " mikeowens at gmail dot com 2023-05-08 22:49 ` mikeowens at gmail dot com 2023-05-09 4:22 ` mikeowens at gmail dot com 2023-05-09 6:03 ` mikeowens at gmail dot com 2023-05-09 14:45 ` [Bug tdep/30430] " tromey at sourceware dot org 2023-05-09 16:33 ` mikeowens at gmail dot com 2023-05-09 21:07 ` mikeowens at gmail dot com 2023-05-09 21:17 ` tromey at sourceware dot org 2023-05-09 21:28 ` mikeowens at gmail dot com 2023-05-09 21:55 ` tromey at sourceware dot org 2023-05-09 22:13 ` mikeowens at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30430-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).