From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Alan Cox <alan@redhat.com>
Cc: Willy Tarreau <willy@w.ods.org>,
Christoph Hellwig <hch@alpha.home.local>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
vda@port.imtp.ilyichevsk.odessa.uay
Subject: Re: i486 emu in mainline?
Date: Tue, 25 May 2004 11:36:52 +0200 [thread overview]
Message-ID: <20040525093652.GA1912@lug-owl.de> (raw)
In-Reply-To: <20040524174156.GG19161@devserv.devel.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
On Mon, 2004-05-24 13:41:56 -0400, Alan Cox <alan@redhat.com>
wrote in message <20040524174156.GG19161@devserv.devel.redhat.com>:
> On Mon, May 24, 2004 at 05:17:15PM +0200, Jan-Benedict Glaw wrote:
> > There are some application that register signal handling functions IIRC
> > for SIGILL, SIGSEGV and the like to do internal error trapping on their
> > own (not only OOo comes to mind). These would probably be f*cked up if they
> > didn't call the LD_PRELOADed signal handler...
>
> No. The LD_PRELOAD also hooks the signal setting functions. This really is
> not rocket science at all.
But works only on dynamically linkes executables, and only on those that
don't do system calls on their own, right?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-25 9:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 23:40 i486 emu in mainline? Christoph Hellwig
2004-05-23 0:20 ` Rene Rebe
2004-05-23 7:13 ` Arjan van de Ven
2004-05-23 8:44 ` Willy Tarreau
2004-05-23 9:13 ` Arjan van de Ven
2004-05-23 9:48 ` Willy Tarreau
2004-05-23 9:58 ` Arjan van de Ven
2004-05-23 11:49 ` Helge Hafting
2004-05-23 9:20 ` Andrew Morton
2004-05-23 17:11 ` Brian Gerst
2004-05-24 2:47 ` Herbert Xu
2004-05-27 21:03 ` Pavel Machek
2004-05-23 8:29 ` Willy Tarreau
2004-05-23 11:08 ` Alan Cox
2004-05-23 11:57 ` Willy Tarreau
2004-05-23 13:15 ` Alan Cox
2004-05-24 15:17 ` Jan-Benedict Glaw
2004-05-24 17:41 ` Alan Cox
2004-05-25 9:36 ` Jan-Benedict Glaw [this message]
2004-05-25 13:48 ` Alan Cox
[not found] ` <20040523105130.GA588@samarkand.rivenstone.net>
2004-05-23 11:59 ` Willy Tarreau
2004-05-24 9:08 ` P
2004-05-23 15:18 ` Jeff Garzik
2004-05-23 21:14 ` Alan Cox
2004-05-24 12:28 ` Maciej W. Rozycki
2004-05-25 17:21 ` Kronos
-- strict thread matches above, loose matches on Subject: below --
2004-05-25 17:03 Albert Cahalan
2004-05-25 22:43 ` Alan Cox
2004-10-10 20:33 Nathanael Nerode
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=20040525093652.GA1912@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=hch@alpha.home.local \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.uay \
--cc=willy@w.ods.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