* Chris Metzler -- Friday 17 March 2006 08:17:
> Melchior FRANZ wrote:
> > * Chris Metzler -- Sunday 26 February 2006 06:20:
> > > } FATAL: PUI: No Live Interface! Forgot to call puInit ?
> > 
> > (free)glut or SDL?
> 
> glut.

You are really using unfree-glut on Debian?  :-}
I just asked because plib does different things for glut & sdl in puInit().


 
> > Can you post a backtrace?
> 
> Apparently not!  (see below)

You can add a simple  *(char *)0 = 0; right before that pui fatal error,
then you should get a bt in any case. (Not necessarily a useful one.)



> (no debugging symbols found)

Not compiled/linked with -g? I'd say that's a prerequisite for debugging.



> FATAL: PUI: No Live Interface! Forgot to call puInit ?

Is this with an antiquated plib? Does it abort before the puInit() call
or after that? (Yes, we are of course calling it -- should be early
enough in the boot process: GUI/gui.cxx:69. Add this line after that

  cerr << "\033[31;1mpuInit() called\033[m" << endl;

and recompile. When I did this and ran fgfs with --log-level=info, then
I got this:

  Finished command line arguments
  Initializing splash screen
  GeForce FX 5500/AGP/SSE2
  Max texture size = 4096
  Depth buffer bits = 24
  puInit() called                        <-------
  Loading Airport Database ...
  Data file version = 810

Can you check that? Ideally also use gdb to step through the init
process and see where it stumbles. (There are front ends that make
this quite comfortable, such as ddd.)

m.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to