This had me fooled.
The call stack seemed to indicate an Nvidia OpenGL bug
But it wasn't.
#2 0x28913b78 in abort () from /lib/libc.so.6
#3 0x2895bc6f in pthread_testcancel () from /lib/libpthread.so.2
#7 0x28a0314d in _nv07gl () from /usr/local/lib/libGL.so.1
#8 0x28a725e4 in ?? () from
Hi Jim,
Unfortunately the stack trace doesn't tell us much beyond its
something related to pthreads, it could be a bug in pthreads itself, a
bug in OpenThreads, or a bug in OSG but we so far have absolutely no
way of telling. You'll need to try and isolate the failure condition
from the top
-Original Message-
From: Jim Brooks [EMAIL PROTECTED]
Sent: Saturday, January 26, 2008 4:30 PM
To: osg-users@lists.openscenegraph.org
Subject: Re: [osg-users] Recurse on a private mutex (FreeBSD)
Could you provide a stack trace and a few more details about when and
where this problems
HI Jim,
Could you provide a stack trace and a few more details about when and
where this problems occurs i.e. which examples and data etc.
Robert.
On Jan 26, 2008 3:52 AM, Jim Brooks [EMAIL PROTECTED] wrote:
Occurs on OSG 2.x on FreeBSD 6.2.
Definitely a FreeBSD-specific problem.
Already
Could you provide a stack trace and a few more details about when and
where this problems occurs i.e. which examples and data etc.
Hi Robert,
abort() was called in pthreads before main() was ever reached.
Happens on two different OSG programs (run fine on Linux/Mac/M$).
OSG 1.2 runs fine on the
Occurs on OSG 2.x on FreeBSD 6.2.
Definitely a FreeBSD-specific problem.
Already tried single-threading.
Fatal error 'Recurse on a private mutex.' at line 986
in file /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 0)
Abort trap: 6
___
osg-users
6 matches
Mail list logo