From owner-freebsd-threads@FreeBSD.ORG Wed Jun 25 06:55:24 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3A9F37B401 for ; Wed, 25 Jun 2003 06:55:24 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A8C143F93 for ; Wed, 25 Jun 2003 06:55:24 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h5PDtMXh023938; Wed, 25 Jun 2003 09:55:22 -0400 (EDT) Date: Wed, 25 Jun 2003 09:55:21 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Alexey Zelkin In-Reply-To: <20030625133041.A12986@phantom.cris.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org Subject: Re: libkse & jdk14: signals(?) breakage X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2003 13:55:25 -0000 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