From: Godmar Back (gback@cs.utah.edu)
Date: Wed Feb 03 1999 - 15:00:43 EST
>
> On Feb 3, 1999, Alexandre Oliva <oliva@dcc.unicamp.br> wrote:
>
> > On Feb 3, 1999, Godmar Back <gback@cs.utah.edu> wrote:
> >>> On Feb 3, 1999, Godmar Back <gback@cs.utah.edu> wrote:
>
> >>> > Isn't making the calls to libltdl thread-safe on our TODO list ever
> >>> > since it was introduced?
>
> >>> They are thread safe, because libnative is dlopened before the
> >>> threading system is started, and, after that, only System.loadLibrary
> >>> will load libraries, but it is already synchronized.
>
> >> If that's so, then how is it possible for VTALRM to screw up things?
>
> > There are two thread initializations in initialiseKaffe:
> > initNativeThreads and initThreads, and initNative runs in between
> > them. I'm not sure when VTALRM is set up...
>
> It's set up in jthread_init(), caled from initNativeThreads(), so it
> is enabled before initNative(), which supports my theory that it is
> interfering somehow.
>
But it does not support your theory that it caused by recent changes,
because that's the way it has always been.
I'll try to reproduce it. What version of Linux/libc were you using?
Also, maybe we should do "repeat 100 strace ..." or somesuch to see
if we get a system call trace of when it happens.
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:56 EDT