From: Mike Frysinger <vapier@gentoo.org>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Set unknown_syscall differently on arm linux
Date: Mon, 04 Jul 2016 02:20:00 -0000 [thread overview]
Message-ID: <20160704021956.GQ4685@vapier.lan> (raw)
In-Reply-To: <CAH=s-PNk8JmbSx5sTNpoJRbTFNWzcfq+fHjQGtxjg=ASVB20EQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
On 30 Jun 2016 15:48, Yao Qi wrote:
> On Thu, Jun 30, 2016 at 1:58 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> > wow, that code is messed up. can you raise a bug with them ? there's
> > even more code paths in there that result in SIGSEGV too. the history
> > predates 2.4.0 afaict.
>
> Sure, I can raise a bug somewhere or ask it in arm kernel mail list, but
> why do you think it is a bug that SIGILL is raised when an illegal/unknown
> syscall number is passed to syscall? because other archs don't behave
> this way?
correct -- i know of no other arch that behaves this way. the syscall
ABI is supposed to communicate errors via return values (which are errno
values), not by sending signals which kill the process.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-07-04 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 9:26 Yao Qi
2016-06-29 9:53 ` Pedro Alves
2016-06-29 13:56 ` Yao Qi
2016-06-29 17:41 ` Mike Frysinger
2016-06-30 7:52 ` Yao Qi
2016-06-30 12:58 ` Mike Frysinger
2016-06-30 14:48 ` Yao Qi
2016-07-04 2:20 ` Mike Frysinger [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160704021956.GQ4685@vapier.lan \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
/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