From: Pip Cet via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 74831@debbugs.gnu.org
Cc: eliz@gnu.org, telegraph@gmx.net
Subject: bug#74831: 31.0.50; scratch/igc: segfaults on startup when called under gdb
Date: Fri, 13 Dec 2024 08:59:33 +0000 [thread overview]
Message-ID: <87pllwgdrs.fsf@protonmail.com> (raw)
In-Reply-To: <86cyhwzq5c.fsf@gnu.org>
"Eli Zaretskii" <eliz@gnu.org> writes:
>> > I think we can close this bug now.
>>
>> Fine with me.
>
> Done.
Sorry to respond to a closed bug report, but I just pushed a change to
README-IGC which mentions the use of SIGSEGV by MPS. While there is
more to be said on the topic (users of lldb on non-macOS systems have to
change signal disposition manually, right now; and solaris/sparc gdb
loses the siginfo information when receiving a SIGSEGV, which means MPS
builds on those systems happen to work but cannot be debugged with gdb),
I've tried to keep it short.
Thanks again for the report!
Pip
prev parent reply other threads:[~2024-12-13 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 14:26 bug#74831: 31.0.50; scratch/igc: segfaults on startup when called under gdb Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 14:53 ` Eli Zaretskii
2024-12-12 16:15 ` Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 16:43 ` Eli Zaretskii
2024-12-12 16:53 ` Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 18:56 ` Eli Zaretskii
2024-12-13 8:59 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pllwgdrs.fsf@protonmail.com \
--to=bug-gnu-emacs@gnu.org \
--cc=74831@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=pipcet@protonmail.com \
--cc=telegraph@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).