Date: Wed, 25 Jun 2003 19:23:26 +0300 From: Alexey Zelkin <phantom@FreeBSD.org.ua> To: Daniel Eischen <eischen@vigrid.com> Cc: threads@freebsd.org Subject: Re: libkse & jdk14: signals(?) breakage Message-ID: <20030625192326.A15424@phantom.cris.net> In-Reply-To: <Pine.GSO.4.10.10306250953210.22247-100000@pcnet5.pcnet.com>; from eischen@vigrid.com on Wed, Jun 25, 2003 at 09:55:21AM -0400 References: <20030625133041.A12986@phantom.cris.net> <Pine.GSO.4.10.10306250953210.22247-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, On Wed, Jun 25, 2003 at 09:55:21AM -0400, Daniel Eischen wrote: > 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. Cool! It really helped. At least visible behaviour is same to libc_r. /me running TCK tests...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030625192326.A15424>