linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Emulating i486 on i386 (was: TSCs are a no-no on i386)
Date: 01 Aug 2003 07:37:55 +0200	[thread overview]
Message-ID: <1059716275.5032.31.camel@workshop.saharacpt.lan> (raw)
In-Reply-To: <20030731153337.GB1873@lug-owl.de>

On Thu, 2003-07-31 at 17:33, Jan-Benedict Glaw wrote:
> On Thu, 2003-07-31 17:09:19 +0200, Martin Schlemmer <azarah@gentoo.org>
> wrote in message <1059664158.5031.26.camel@workshop.saharacpt.lan>:
> > On Thu, 2003-07-31 at 15:01, Jan-Benedict Glaw wrote:
> > > On Thu, 2003-07-31 14:14:48 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de>
> > > wrote in message <20030731121448.GW1873@lug-owl.de>:
> > > > On Thu, 2003-07-31 12:51:09 +0100, Alan Cox <alan@lxorguk.ukuu.org.uk>
> > > > wrote in message <1059652268.16608.8.camel@dhcp22.swansea.linux.org.uk>:
> > > > > On Iau, 2003-07-31 at 12:38, Jan-Benedict Glaw wrote:
> > > So there we are. Thanks to someone who pointed me to LD_DEBUG et al., I
> > > see that my _init() is called too late:
> > > 
> > > amtus:~/sigill_catcher# LD_DEBUG=all LD_VERBOSE=1
> > > LD_PRELOAD=./libsigill.so apt-get update 2> ld_infos                                 
> > > Illegal instruction
> > > amtus:~/sigill_catcher# grep 'calling init' ld_infos 
> > > 00691:  calling init: /lib/libc.so.6
> > > 00691:  calling init: /lib/libdl.so.2
> > > 00691:  calling init: /lib/libgcc_s.so.1
> > > 00691:  calling init: /lib/libm.so.6
> > > 00691:  calling init: /usr/lib/libstdc++.so.5
> > > 
> > > As I guessed, libstdc++5's _init() is called before mine (LD_PRELOADed)
> > > _init() function and thus, I cannot intercept this SIGILL, as it
> > > seems...
> > > 
> > 
> > You could do what we do with our path sandbox - basically you
> > use a wrapper that setup the environment (prob not needed in
> > your case), and then spawn bash with our sandbox lib preloaded,
> > which then calls whatever should be 'path sandboxed'.
> 
> Care to send some URL? I haven't found it ad hoc by Google...
> 

http://www.gentoo.org/cgi-bin/viewcvs.cgi/portage/src/sandbox-1.1/?cvsroot=gentoo-src


Cheers,

-- 
Martin Schlemmer
Gentoo Linux Developer, Desktop Team
Cape Town, South Africa


  reply	other threads:[~2003-08-01  5:41 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 13:56 TSCs are a no-no on i386 Jan-Benedict Glaw
2003-07-30 14:18 ` Maciej W. Rozycki
2003-07-30 14:44   ` Jan-Benedict Glaw
2003-07-30 16:58 ` Matthew Garrett
2003-07-30 17:19   ` Alan Cox
2003-07-30 18:10 ` Adrian Bunk
2003-07-30 18:30   ` Mike Fedyk
2003-07-30 18:45     ` Adrian Bunk
2003-07-30 20:01       ` Alan Cox
2003-07-30 20:33         ` Jan-Benedict Glaw
2003-07-30 22:19           ` J.A. Magallon
2003-07-31  6:11             ` Jan-Benedict Glaw
2003-07-30 23:05           ` Alan Cox
2003-07-31 11:11             ` Richard B. Johnson
2003-07-31 11:26               ` Emulating i486+ insn on i386 (was: TSCs are a no-no on i386) Jan-Benedict Glaw
2003-07-31 11:41             ` TSCs are a no-no on i386 Jan-Benedict Glaw
2003-07-31  0:22           ` Adrian Bunk
2003-07-31  6:22             ` Jan-Benedict Glaw
2003-07-31  7:17               ` Willy Tarreau
2003-07-31 11:38                 ` Emulating i486 on i386 (was: TSCs are a no-no on i386) Jan-Benedict Glaw
2003-07-31 11:51                   ` Alan Cox
2003-07-31 12:14                     ` Jan-Benedict Glaw
2003-07-31 13:01                       ` Jan-Benedict Glaw
2003-07-31 15:09                         ` Martin Schlemmer
2003-07-31 15:33                           ` Jan-Benedict Glaw
2003-08-01  5:37                             ` Martin Schlemmer [this message]
2003-07-31 15:12                     ` Jamie Lokier
2003-07-31 15:32                       ` Jan-Benedict Glaw
2003-07-31 15:07                 ` TSCs are a no-no on i386 Jamie Lokier
2003-07-31 15:23                   ` Willy Tarreau
2003-07-31 15:50                   ` Richard B. Johnson
2003-07-31 16:24                     ` Jan-Benedict Glaw
2003-08-06 11:08         ` Pavel Machek
2003-08-06 14:33           ` Maciej W. Rozycki
2003-07-30 20:28       ` Jan-Benedict Glaw
2003-07-30 21:50         ` Petr Vandrovec
2003-07-30 23:10           ` Alan Cox
2003-07-31 15:10             ` Jamie Lokier
2003-07-31 16:01               ` Alan Cox
2003-07-31 18:37                 ` Jamie Lokier
2003-07-31 19:10                   ` Alan Cox
2003-07-31  6:29           ` Jan-Benedict Glaw
2003-07-30 20:27   ` Jan-Benedict Glaw
     [not found] <f41P.374.9@gated-at.bofh.it>
     [not found] ` <f4bw.3eu.13@gated-at.bofh.it>
     [not found]   ` <f5Az.4tG.3@gated-at.bofh.it>
     [not found]     ` <f5TZ.4Hq.11@gated-at.bofh.it>
     [not found]       ` <f9uz.Ll.5@gated-at.bofh.it>
     [not found]         ` <ff6X.6qi.3@gated-at.bofh.it>
     [not found]           ` <ffTk.734.15@gated-at.bofh.it>
     [not found]             ` <fk6A.241.7@gated-at.bofh.it>
     [not found]               ` <fkgp.2aL.29@gated-at.bofh.it>
     [not found]                 ` <fnnW.4QQ.43@gated-at.bofh.it>
     [not found]                   ` <fnQP.5bE.5@gated-at.bofh.it>
2003-07-31 17:35                     ` Emulating i486 on i386 (was: TSCs are a no-no on i386) Ben Pfaff

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=1059716275.5032.31.camel@workshop.saharacpt.lan \
    --to=azarah@gentoo.org \
    --cc=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).