Re: intercepting system calls?
Re: intercepting system calls?
- Subject: Re: intercepting system calls?
- From: Erik Paulson <email@hidden>
- Date: Tue, 24 Jan 2006 15:17:18 -0600
On Mon, Jan 23, 2006 at 02:01:20PM -0800, Mike Smith wrote:
>
> Ok; here's where we got a bit of a disconnect. The runtime environment
> on Mac OS (which is primarily what Darwin lives to support) is a lot
> more
> complicated than that on something like Linux (unless you bring KDE
> into the picture, and even then...).
>
> It's not sufficient in the general sense to redirect a single
> application; there
> are quite a large number of situations in which work is done for an
> application
> by proxy, and to have that happen correctly the proxy has to have
> relevant
> context.
>
I'm not trying to support every possible application, just a few. Most
of what I want to run will be things like legacy FORTRAN and C console
programs. I don't want to run iTunes :)
> Now, arguably you can redirect the proxy requests, but now you're
> talking
> about handling distributed shared memory as well, and don't forget the
> heavy use of Mach-style messaging.
>
Again, I don't expect to see a lot of those. I'm perfectly willing to
abort a program when it runs and tries to execute a system call that I'm
not prepared to handle.
<...>
> >Such an unprivileged interface doesn't appear to exist, short of some
> >sort of binary rewriting or single stepping.
>
> You can achieve this with the dynamic linker interfaces already
> mentioned.
>
With the caveat that the dynamic linker gives no feedback when I miss an
interface. Trapping system calls means that I can see every byte that goes
in and out of a processes address space.
-Erik
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden