protecting malloc(), etc

Date view Thread view Subject view Author view

From: Archie Cobbs (archie@whistle.com)
Date: Fri Feb 05 1999 - 01:39:50 EST


Godmar et. al.,

Regarding this problem of protecting non-reentrant libc routines
(like malloc()) with mutex's... it seems like we should apply
some kind of immediate fix now, even if a less than optimal one.
Then we can work out optimizations later.

My ulterior motive here is that we're trying to get Apache
working with jserv, and it's working OK but bombing out with
"recursive malloc" errors.

What would be the simplest thing we could slap on there for
the time being? I'd be willing to do it if you can explain
how it can be done simply.

By the way, I don't think the JNI spec says anything about
whether native code can expect to be protected from preemption.
Does anyone know more about this? If not, we have to protect
all native calls anyway.

-Archie

___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:58 EDT