On Tue, 2003-03-18 at 10:07, Ed Schaller wrote: > Hum.. I don't think that it is possible to do something like this in any > easy way. Anything you dlopen is executing in the same process space and > the kernel sees no difference between the original process and the code > you've loaded. About the best that you could do is fork off another > process, blank out the memory you don't want it seeing (it will be > able to write stuff anyway) and use ulimit to limit the ram for the > whole process.
Yeah, looks like a seperate process is the only solution. That's reasonable, no real need to reinvent the wheel when you've already got protected process memory and rich IPC options. Instead of clearing memory, I'm just going to make sure it's never there in the first place. I plan on writing a minimalistic loader/driver. Basically: fork, exec loader, dlopen, communicate using the simplest type of IPC for the problem. -- Stuart Jansen <[EMAIL PROTECTED]> #define FALSE 0 /* This is the naked Truth */ #define TRUE 1 /* and this is the Light */ -- mailto.c ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://phantom.byu.edu/cgi-bin/mailman/listinfo/uug-list
