public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/29546] sigdescr_np for SIGEMT is useless
Date: Tue, 06 Sep 2022 01:04:51 +0000 [thread overview]
Message-ID: <bug-29546-131-I34bGCQauD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29546-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29546
--- Comment #2 from Bruno Haible <bruno at clisp dot org> ---
> In what context did you come across this signal, and why was the string "EMT" not descriptive there?
I haven't seen this signal being sent to a process. Rather, I was looking at
the meta-information, namely how to best define sigdescr_np for Gnulib.
On Linux/SPARC, it seems to be used for "tagged arithmetic overflow".
On Linux/MIPS, for MIPS R2 instruction emulation.
On Hurd, it is what the Mach error EXC_EMULATION ("Emulation support
instruction encountered") translates to.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-06 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 11:40 [Bug string/29546] New: " bruno at clisp dot org
2022-09-03 11:41 ` [Bug string/29546] " bruno at clisp dot org
2022-09-05 11:34 ` fweimer at redhat dot com
2022-09-06 1:04 ` bruno at clisp dot org [this message]
2022-09-06 10:31 ` fweimer at redhat dot com
2022-09-06 11:01 ` bruno at clisp dot org
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-29546-131-I34bGCQauD@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).