From: Mike Frysinger <vapier@gentoo.org>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Set unknown_syscall differently on arm linux
Date: Wed, 29 Jun 2016 17:41:00 -0000 [thread overview]
Message-ID: <20160629174103.GW4685@vapier.lan> (raw)
In-Reply-To: <1467105996-18063-1-git-send-email-yao.qi@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
On 28 Jun 2016 10:26, Yao Qi wrote:
> Currently, we use 123456789 as unknown or illegal syscall number, and
> expect program return ENOSYS. Although 123456789 is an illegal syscall
> number on arm linux, kernel sends SIGILL rather than returns -ENOSYS.
err, what ? calling random syscalls should not result in signals being
generated (ignoring obvious ones like __NR_kill). is the kernel broken ?
i think this needs more investigation & explanation.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-29 17:41 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 [this message]
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
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=20160629174103.GW4685@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