public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/30430] SIGABRT on run (Illumos on SPARC)
Date: Tue, 09 May 2023 14:45:35 +0000 [thread overview]
Message-ID: <bug-30430-4717-oonBAu86kl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30430-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30430
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c++ |tdep
CC| |tromey at sourceware dot org
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Mike Owens from comment #0)
> This is specifically a SPARC issue. I am running the latest OpenIndiana on a
> T4-1.
I suspect it's more about the OS than the architecture.
I know other sparc ports work ok.
Unfortunately I don't think anybody is actively maintaining this port.
So, it's possible that either it needs some changes for more recent versions
of the OS, or that the code in gdb bit-rotted a bit as other gdb changes
were made.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-09 14:45 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 ` [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 ` tromey at sourceware dot org [this message]
2023-05-09 16:33 ` [Bug tdep/30430] " 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-oonBAu86kl@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).