From: Corey Minyard <minyard@acm.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Change to allow signal handlers to set SE and BE bits.
Date: Tue, 09 Sep 2003 16:34:01 -0500 [thread overview]
Message-ID: <3F5E4749.6080105@acm.org> (raw)
In-Reply-To: <1063136371.642.44.camel@gaston>
What if you went back to using the original syscall numbers? Those seem
to have code in gdb to support them.
-Corey
Benjamin Herrenschmidt wrote:
>On Tue, 2003-09-09 at 21:19, Corey Minyard wrote:
>
>
>>Paul came up with a much better method for this. I have added a syscall
>>that does a "debug" return from the signal handler. It's much cleaner.
>>
>>I ahve a patch for this, and I've done a number of things besides just
>>this. I seemed bad to me to add yet another kludge to the beginning of
>>DoSyscall for handling yet another signal return value. So I turned all
>>the signal return syscalls into normal syscalls. This should speed up
>>normal syscall handling by removing four instructions from the syscall
>>entry. Is this ok?
>>
>>
>
>The problem with changing the signal return is that you break at least
>gdb, and maybe more (g++ stack unwinding ?)
>
>Ben.
>
>
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-09 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 20:00 Change to allow signal handlers to set SE and BE bits Corey Minyard
2003-08-29 20:18 ` Matt Porter
2003-09-04 14:16 ` Corey Minyard
2003-09-05 15:23 ` Corey Minyard
2003-09-09 19:19 ` Corey Minyard
2003-09-09 19:39 ` Benjamin Herrenschmidt
2003-09-09 21:34 ` Corey Minyard [this message]
2003-09-10 1:37 ` Paul Mackerras
2003-09-10 2:47 ` Corey Minyard
2003-08-30 0:29 ` Paul Mackerras
2003-09-01 20:46 ` Corey Minyard
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=3F5E4749.6080105@acm.org \
--to=minyard@acm.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.