* Brian F. Feldman <[EMAIL PROTECTED]> [010424 05:07] wrote:
> In some way, using Linux LinuxThreads programs that use shared memory, I've
> ended up with dozens of shared memory segments that reportedly still have 1
> attachment (which I'm really darn certain is impossible since I've killed
> _everything_ in sight). I think something must have happened that for some
> reason shmexit() was not called on process exit, vm_shm refcnt was increased
> too many times, vm_shm refcnt was not decreased enough times... whatever the
> case, there may be an old vmspace just floating around stranded, or just a
> simple bug with vm_shm...
>
> Does anyone have any clues about races or weird issues in this area? It's
> pretty exasperating to not be able to figure this one out. I don't
> immediately see any obvious races after half an hour of searching (since it
> appears all calls that can modify vmspace directly require Giant being held).
sysv_shm registers atexit and atfork handlers, perhaps you can stick
some debugging code in there?
--
-Alfred Perlstein - [[EMAIL PROTECTED]]
Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
