This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Set unknown_syscall differently on arm linux

From: Mike Frysinger <vapier at gentoo dot org>
To: Yao Qi <qiyaoltc at gmail dot com>
Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
Date: Sun, 3 Jul 2016 22:19:56 -0400
Subject: Re: [PATCH] Set unknown_syscall differently on arm linux
Authentication-results: sourceware.org; auth=none
References: <1467105996-18063-1-git-send-email-yao dot qi at linaro dot org> <20160629174103 dot GW4685 at vapier dot lan> <CAH=s-PNROPwycGYFZ1_Duc4SRN4vCXHuuX+ootCT3bMD5SOEkw at mail dot gmail dot com> <20160630125840 dot GB4685 at vapier dot lan> <CAH=s-PNk8JmbSx5sTNpoJRbTFNWzcfq+fHjQGtxjg=ASVB20EQ at mail dot gmail dot com>

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: signature.asc
Description: Digital signature

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]