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] SIGABRT on run (Illumos on SPARC)
Date: Mon, 08 May 2023 21:20:51 +0000	[thread overview]
Message-ID: <bug-30430-4717-aCYGVnwo0Z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30430-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30430

--- Comment #1 from Mike Owens <mikeowens at gmail dot com> ---
If I run this as root with truss, I get a slightly different (shorter) result.
In both cases it seems the signal is being issued on read():


    /1:     open("/lib/sparcv9/libc.so.1-gdb.gdb", O_RDONLY|O_CLOEXEC) Err#2
ENOENT
    /1:     open("/opt/local/lib/debug/lib/sparcv9/libc.so.1-gdb.gdb",
O_RDONLY|O_CLOEXEC) Err#2 ENOENT
    /1:    
open("/opt/local/share/gdb/auto-load/lib/sparcv9/libc.so.1-gdb.gdb",
O_RDONLY|O_CLOEXEC) Err#2 ENOENT
    /1:     resolvepath("/lib/sparcv9/libc.so.1", "/lib/sparcv9/libc.so.1",
1024) = 22
    /1:     open("/lib/sparcv9/libc.so.1-gdb.py", O_RDONLY|O_CLOEXEC) Err#2
ENOENT
    /1:     open("/opt/local/lib/debug/lib/sparcv9/libc.so.1-gdb.py",
O_RDONLY|O_CLOEXEC) Err#2 ENOENT
    /1:     open("/opt/local/share/gdb/auto-load/lib/sparcv9/libc.so.1-gdb.py",
O_RDONLY|O_CLOEXEC) Err#2 ENOENT
    /1:     lseek(14, 0xFFFFFFFFFFFE0228, SEEK_CUR)         = 306960
    /1:     close(14)                                       = 0
    /1:     open("/lib/sparcv9/libc.so.1", O_RDONLY)        = 14
    /1:     fcntl(14, F_GETFD, 0x00000000)                  = 0
    /1:     fcntl(14, F_SETFD, 0x00000001)                  = 0
    /1:     lseek(14, 1467912, SEEK_SET)                    = 1467912
    /1:     fstat(14, 0xFFFFFFFF7FFEFFC0)                   = 0
    /1:     fstat(14, 0xFFFFFFFF7FFEFDE0)                   = 0
    /1:     ioctl(14, TCGETA, 0xFFFFFFFF7FFEFEFE)           Err#25 ENOTTY
    /1:     read(14, "7F D O F02020102\b\b\0\0".., 131072)  = 131072
    /1:     sigaction(SIGABRT, 0x00000000, 0xFFFFFFFF7FFEC290) = 0
    /1:     lseek(14, 0xFFFFFFFFFFFE1DC0, SEEK_CUR)         = 1475528
    /1:     sigaction(SIGABRT, 0xFFFFFFFF7FFEC0B0, 0xFFFFFFFF7FFEC1A0) = 0
    /1:     lwp_sigmask(SIG_SETMASK, 0x00000000, 0x00000000, 0x00000000,
0x00000000) = 0xFFBFFEFF [0xFFFFFFFF]
    /1:     lwp_kill(1, SIGABRT)                            = 0
    /1:         Received signal #6, SIGABRT [default]
    /1:           siginfo: SIGABRT pid=20523 uid=0 code=-1

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2023-05-08 21:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 21:02 [Bug c++/30430] New: " mikeowens at gmail dot com
2023-05-08 21:20 ` mikeowens at gmail dot com [this message]
2023-05-08 22:49 ` [Bug c++/30430] " 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-aCYGVnwo0Z@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: link
Be 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).