Re: protecting malloc(), etc

Date view Thread view Subject view Author view

From: Godmar Back (gback@cs.utah.edu)
Date: Fri Feb 05 1999 - 01:59:24 EST


>
> Archie Cobbs writes:
> > 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.
>
> OR, make it clear that native routines are responsible for
> doing this themselves (which might make more sense).
>
> After thinking about it some more, there probably aren't
> *that* many libc calls that kaffe really uses, at least
> in the core part. So maybe the best strategy is just to
> identify these and wrap them in a macro or whatever.
>

That's my thinking too. In fact, there shouldn't be any in the core
and the native libraries. It's different for the awt, but jserv doesn't
use that.

Unfortunately, libltdl uses stdio, although it didn't look like that
would be hard to fix.
I must admit I don't know about sprintf: is it async-signal-safe?
I'll look at the POSIX book tomorrow.

The Linux stuff is still really weird.

        - Godmar


Date view Thread view Subject view Author view

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