From: Godmar Back (gback@cs.utah.edu)
Date: Sat Feb 06 1999 - 23:21:10 EST
>
> That should only be a problem if we actually context-switched or
> called some library function from within the signal handler, but we
> apparently don't. Unless dlopen modifies some global symbol table in
> a way that calling unrelated code may crash. In this case, we'd have
> to block signals before dlopening anything. This would probably be a
> good idea in general. Is blocking signals part of the threading API?
>
Like I just said, we should make it part of it.
I'll add a blockAsyncSignals() in jsignal.h
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:59 EDT