On jeu 28 août 2008, Durk Talsma wrote:
Hi Tim,
On Wednesday 27 August 2008 15:37:19 Tim Moore wrote:
This is great! We can't call osgDB:SharedStateManager::share from the
database pager thread. I'll check in a fix soon.
Great to hear that this stack trace was useful. :-)
Cheers,
Durk
Hi Tim,
On Wednesday 27 August 2008 15:37:19 Tim Moore wrote:
This is great! We can't call osgDB:SharedStateManager::share from the
database pager thread. I'll check in a fix soon.
Great to hear that this stack trace was useful. :-)
Cheers,
Durk
Durk Talsma wrote:
FWIW, I;m seeing an occasional segfault. Today, I managed to trap it using
gdb. below is the complete stack trace. IIRC, 2D texture loading has been
giving occasional problems. This particular error occurred in my new traffic
manager version of Flightgear. It doesn't
On Sunday 24 August 2008 04:38:36 Csaba Halász wrote:
At least 3 of us get immediate segfault most of the time if starting
at LFPG. I got various backtraces, mostly from OSG.
Sometimes there is a warning similar to this:
Warning: deleting still referenced object 0xb2de7f08 of type
On Sun, Aug 24, 2008 at 04:38:36AM +0200, Csaba Halász wrote:
At least 3 of us get immediate segfault most of the time if starting
at LFPG. I got various backtraces, mostly from OSG.
Me too , i have many segfaults . My context :
- Phenom 9750 Quad-Core / GeForce 8800 GT
- linux 2.6.25 (
At least 3 of us get immediate segfault most of the time if starting
at LFPG. I got various backtraces, mostly from OSG.
Sometimes there is a warning similar to this:
Warning: deleting still referenced object 0xb2de7f08 of type
'PN3osg10ReferencedE'
the final reference count was 0, memory
On Sun, 2008-08-24 at 04:38 +0200, Csaba Halász wrote:
At least 3 of us get immediate segfault most of the time if starting
at LFPG. I got various backtraces, mostly from OSG.
Sometimes there is a warning similar to this:
Warning: deleting still referenced object 0xb2de7f08 of type
7 matches
Mail list logo
