From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Ivan Zakharyaschev <imz@altlinux.org>
Cc: bug-gnulib@gnu.org, Andrey Savchenko <bircoph@altlinux.org>,
Bruno Haible <bruno@clisp.org>
Subject: Re: [RFC PATCH] test-c-stack2.sh: skip if the platform sent SIGILL on an invalid address.
Date: Sat, 29 Dec 2018 19:30:51 +0300 [thread overview]
Message-ID: <20181229163051.GB22735@altlinux.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1812291505000.6081@imap.altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On Sat, Dec 29, 2018 at 06:03:42PM +0300, Ivan Zakharyaschev wrote:
[...]
> BTW, saving and forgetting the type of the original fault doesn't seem
> to be something expensive to implement (after some thought): when a
> register is marked as invalid, it shouldn't matter anymore what value
> it holds. So, the same register can be used to save the information
> about the type of the fault.
Note that SIGILL, SIGFPE, SIGSEGV, and SIGBUS come with si_addr specifying
the memory location which caused the fault. When memory fault is
transformed into illegal operand failt, the location of the original
memory fault is likely lost, too - you can easily check this hypothesis
by installing a signal handler: if si_addr is not 0xbad from your example,
then it's been lost.
--
ldv
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-12-29 17:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 12:50 [RFC PATCH] test-c-stack2.sh: skip if the platform sent SIGILL on an invalid address Ivan Zakharyaschev
2018-12-20 2:24 ` Bruno Haible
2018-12-28 14:23 ` Ivan Zakharyaschev
2018-12-29 11:17 ` Bruno Haible
2018-12-29 11:31 ` Andrey Savchenko
2018-12-29 14:03 ` Bruno Haible
2018-12-29 14:31 ` Dmitry V. Levin
2018-12-29 14:54 ` Bruno Haible
2018-12-29 15:03 ` Ivan Zakharyaschev
2018-12-29 16:30 ` Dmitry V. Levin [this message]
2018-12-29 20:13 ` Ivan Zakharyaschev
2018-12-30 4:49 ` Bruno Haible
2018-12-29 13:54 ` Dmitry V. Levin
2018-12-29 15:15 ` Ivan Zakharyaschev
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181229163051.GB22735@altlinux.org \
--to=ldv@altlinux.org \
--cc=bircoph@altlinux.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=imz@altlinux.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).