libkse & jdk14: signals(?) breakage
Daniel Eischen
eischen at vigrid.com
Wed Jun 25 06:55:25 PDT 2003
On Wed, 25 Jun 2003, Alexey Zelkin wrote:
> hi,
>
> Yesterday I have got to point then libkse & libthr testing
> reached top of my TODO list. Results are not that I expected and
> wanted to get.
>
> In my first expirement I have had 6 Jun's -CURRENT and very recent
> libkse and libthr. In this case at jdk14 build attempt I have
> expirienced strange behaviour of both libs: at compiling of big
> chunks of code java compiler stuck in "pause" mode forever.
>
> Well, I have made clean build & install with most recent world,
> kernel and libkse and found that "pause" lockups are not repearing
> anymore, but something still broken. While compiling of one of
> packages it's usual case then SIGSEGV is received by javac. In
> libc_r case it is usually catched by signalHandler(), handled
> and continued. But in libkse case signal is not even reached
> of signalHandler() routine. As soon as I do 'continue' in gdb
> I get another SIGSEGV with below backtrace.
>
> Looks like signals are still not really working in libkse.
David Xu is revamping signal handling (it also involves
some kernel changes). Very alpha patches are at:
http://people.freebsd.org/~davidxu/kse_sig/
They are not yet completely working, but might help.
--
Dan Eischen
More information about the freebsd-threads
mailing list