On Monday 17 January 2005 22:12, Melchior FRANZ wrote:
> * Curtis L. Olson -- Monday 17 January 2005 21:59:
> > Any chance you can get us a gdb backtrace?
>
> I can reproduce the crash, though. I'll look into it ...
>
> m.
Thanks Melchior. Anyways, here's my backtrace: Just out of curiosity: Would it
be the case that the loader fails because it doesn't have a path to read data
from? This is a bit of a wild guess, because I didn't have time to look into
the code at all.
Cheers,
Durk
Starting program: /home/durk/src/FlightGear-0.9/source-clean/src/Main/fgfs
[New Thread 16384 (LWP 1634)]
Failed to find runway 28R at airport EHAM
[New Thread 32769 (LWP 1635)]
[New Thread 16386 (LWP 1636)]
Object PanelInstruments not found
Object ControlsGroup not found
[New Thread 32771 (LWP 1637)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16386 (LWP 1636)]
sgGenTile(std::string const&, SGBucket, Point3D*, double*, SGMaterialLib*,
ssgBranch*) ([EMAIL PROTECTED], b=
{cx = 2.1290598554044618e-313, cy = 54.183372497527387, lon = 4, lat =
52, x = 3, y = 2}, center=0x4b71bbfc, bounding_radius=0x0, matlib=0x967ce20,
geometry=0xd8eaf30) at basic_string.h:249
249 { return _M_dataplus._M_p; }
(gdb)
(gdb) bt
#0 sgGenTile(std::string const&, SGBucket, Point3D*, double*, SGMaterialLib*,
ssgBranch*) ([EMAIL PROTECTED], b=
{cx = 2.1290598554044618e-313, cy = 54.183372497527387, lon = 4, lat =
52, x = 3, y = 2}, center=0x4b71bbfc, bounding_radius=0x0, matlib=0x967ce20,
geometry=0xd8cecb0) at basic_string.h:249
#1 0x08305168 in FGTileEntry::load(std::vector<std::string,
std::allocator<std::string> > const&, bool) (this=0xda3db68,
[EMAIL PROTECTED])
at globals.hxx:269
#2 0x082f9dd3 in FGTileLoader::LoaderThread::run() (this=0x8f0d198)
at FGTileLoader.cxx:172
#3 0x0840888f in start_handler (arg=0x0) at SGThread.cxx:23
#4 0x40039f60 in pthread_start_thread () from /lib/i686/libpthread.so.0
#5 0x4003a0fe in pthread_start_thread_event () from /lib/i686/libpthread.so.0
#6 0x4059d327 in clone () from /lib/i686/libc.so.6
(gdb)
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
