Jon Stockill

> 
> Harald JOHNSEN wrote:
> > Jon Stockill wrote:
> >
> >> Due to the death of the machine I was doing all my flightgear work on
> >> I'm currently trying to set up another machine so I can still build
> >> packages, but I've run into a bit of a problem. While my old packages
> >> work ok on this machine (it's not gonna win any awards for framerates,
> >> but it proves it works) the current cvs code segfaults on startup like
> >> this:
> >>
> >> Program received signal SIGSEGV, Segmentation fault.
> >> [Switching to Thread 16384 (LWP 18753)]
> >> 0x401861b2 in _glthread_SetTSD () from /usr/X11R6/lib/libGL.so.1
> >> (gdb) bt
> >> #0  0x401861b2 in _glthread_SetTSD () from /usr/X11R6/lib/libGL.so.1
> >> #1  0x401863f3 in glXCreateGLXPbufferSGIX () from
> >> /usr/X11R6/lib/libGL.so.1
> >
> >
> >
> >> #2  0x0846a17a in RenderTexture::Initialize (this=0x891d220, width=1,
> >>     height=1075494657, shareObjects=false, copyContext=false)
> >>     at RenderTexture.cpp:508
> >
> >
> > You are not supposed to have this width and height, in the bbcache.cxx
> > code there is
> > rt->Initialize(256, 256, true);
> 
> This gets stranger and stranger. I rebuilt the code from scratch
> (suggested by Harald), and it still failed with the same error. So I
> deleted the whole thing, and checked it all out from CVS again - a
> completely clean start. Same error. Checked out the code on another
> machine, built it, runs ok. Copied the binary from the working machine
> to the problem machine, and now the error is back - same binary,
> different machines, different result - a segfault caused by an out of
> range value which is supposed to be hard coded.
> 
> Tests so far have ruled out plib/simgear/flightgear version problems,
> and compiler problems (since the working binary fails on the problem
> system).
> 
> Does anyone have any idea where I should be looking before I go
> completely insane?
> 

No, but if it's any compensation, cvs has been broken under Cygwin since,
well, I've tracked it back to around 7th Jul. For me it started when I
downloaded a clean copy. Norman Vine's version is exiting as soon as the
load sequence finishes, mine and a machine AJ is testing on hangs at the
same point.  At the moment the problem seems to be in Simgear, possibly in
Harald's new GL stuff, but that's a very tentative diagnosis. Right now I
can't see anything obviously wrong, and am really at a loss as to what to do
next. The last known good seems to be 7th Jul - you might like to roll cvs
(FG and SG) back to that point and see what happens.

I'd be interested to compare notes

Vivian 



_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to