From owner-freebsd-threads@FreeBSD.ORG Wed Jun 25 03:23:19 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 1D51737B401 for ; Wed, 25 Jun 2003 03:23:19 -0700 (PDT) Received: from relay1.cris.net (relay1.cris.net [212.110.128.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5658743FDF for ; Wed, 25 Jun 2003 03:23:15 -0700 (PDT) (envelope-from phantom@phantom.cris.net) Received: from phantom.cris.net (root@phantom.cris.net [212.110.130.74]) by relay1.cris.net (8.12.6/8.12.6) with ESMTP id h5PDQcnp011127 for ; Wed, 25 Jun 2003 13:26:39 GMT Received: (from phantom@localhost) by phantom.cris.net (8.12.6/8.12.2) id h5PAUfrx012995; Wed, 25 Jun 2003 13:30:41 +0300 (EEST) (envelope-from phantom) Date: Wed, 25 Jun 2003 13:30:41 +0300 From: Alexey Zelkin To: threads@freebsd.org Message-ID: <20030625133041.A12986@phantom.cris.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.7-STABLE i386 Subject: 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 10:23:19 -0000 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. ps: I'll do same checking against libthr soon and notice you results. [..] Program received signal SIGSEGV, Segmentation fault. 0x28089e9b in __sys_sigprocmask () from /usr/lib/libkse.so.1 (gdb) bt full #0 0x28089e9b in __sys_sigprocmask () from /usr/lib/libkse.so.1 No symbol table info available. #1 0x28082c60 in kse_check_signals (curkse=0x8051000) at /home/phantom/src5/lib/libpthread/thread/thr_kern.c:1028 sigset = {__bits = {134549504, 134549664, 0, 134549508}} i = 134569876 #2 0x280828c0 in kse_sched_multi (curkse=0x8051000) at /home/phantom/src5/lib/libpthread/thread/thr_kern.c:884 curthread = (struct pthread *) 0x8058000 td_wait = (struct pthread *) 0x0 curframe = (struct pthread_sigframe *) 0x2edfe17b ret = 0 #3 0x08051000 in ?? () No symbol table info available. [..]