Date: Thu, 6 Apr 2006 23:41:46 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: kurt@intricatesoftware.com Cc: freebsd-java@freebsd.org Subject: Re: Diablo 1.5 SIGBUS Message-ID: <Pine.GSO.4.43.0604062340380.13286-100000@sea.ntplx.net> In-Reply-To: <200604062329.12999.lists@intricatesoftware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 6 Apr 2006, Kurt Miller wrote: > On Thursday 06 April 2006 8:49 pm, odela01 wrote: > > I applied the patch and did "make all install" in /usr/src/lib/libpthread, > > but it didn't make any difference. I'll try to arrange access to the core > > dump. > > > > Thanks for making the core dump available to me. It was > helpful. I got a partial stack trace from it: > > #0 0x280aa41b in pthread_setcancelstate () from /usr/lib/libpthread.so.2 > #1 0x280a29a6 in pthread_mutexattr_init () from /usr/lib/libpthread.so.2 > #2 0x00000000 in ?? () > > This bt also supports Dan Nelson's observations that this > could be a threading issue. It would be great if you or Dan > built a debug pthreads by commenting the CFLAGS+= -g line in > /usr/src/lib/pthreads/Makefile and rebuilding/reinstall > pthreads. The back-trace from the core file would contain > line numbers and be more useful then. That stack trace doesn't help. pthread_mutexattr_init(), doesn't call pthread_setcancelstate(). Is there any fork()ing going on? -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0604062340380.13286-100000>