Date: Fri, 30 May 2003 15:24:06 -0400 (EDT) From: Daniel Eischen <eischen@pcnet.com> To: Martin Blapp <mb@imp.ch> Cc: freebsd-threads@freebsd.org Subject: Re: panic during openoffice build with libkse Message-ID: <Pine.GSO.4.10.10305301521240.28875-100000@pcnet5.pcnet.com> In-Reply-To: <20030530211205.U94836@cvs.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 30 May 2003, Martin Blapp wrote: > > Hi all, > > > Well, Martin compiles and _runs compiled tools during the office build. > > So libkse can reboot the machine :) > > This is definitly true. The build tools heavily use threads, and I > always had some of the tools breaking with either libc_r or now > libkse, libthr. We found one bug this way for libkse. > > > BTW, I can reliably crash libkse programs on a SMP box using a trivial > > code snippet. It looks like kernel is trying to lock an uninitialized or > > freed mutes and dies with trap 12 while holding a sched_lock spinlock. > > Not a pretty sight. The offending line is kern_mutex.c:598. Sorry, no > > backtrace yet thanks to schedlock. > > I just finished a build of OpenOffice and it seems to run fine ! Mine is built, but the damn thing won't install. This is a fresh installation of openoffice, so there was no prior installation of it. First it bombed on not finding OpenOffice.org1.0, so a did a 'mkdir /usr/local/OpenOffice.org1.0' and it got past that. Now it's stopping in other places. What magic am I missing? > What about HTT ? Can we use that to emulate several cpu's ? I think so. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10305301521240.28875-100000>