Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Yao Qi <qiyaoltc@gmail.com>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Set unknown_syscall differently on arm linux
Date: Thu, 30 Jun 2016 14:48:00 -0000	[thread overview]
Message-ID: <CAH=s-PNk8JmbSx5sTNpoJRbTFNWzcfq+fHjQGtxjg=ASVB20EQ@mail.gmail.com> (raw)
In-Reply-To: <20160630125840.GB4685@vapier.lan>

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?

-- 
Yao (齐尧)


  reply	other threads:[~2016-06-30 14:48 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 [this message]
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='CAH=s-PNk8JmbSx5sTNpoJRbTFNWzcfq+fHjQGtxjg=ASVB20EQ@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@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