* Durk Talsma -- Monday 17 January 2005 22:31:
> 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,
Wild, indeed. But exactly this seems to be the case. My bad. Yes, it's going
to be an fgfs fix. Give me a few minutes ...
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
* 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.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mai
Melchior FRANZ wrote:
* Curtis L. Olson -- Monday 17 January 2005 21:36:
As a result, FlightGear quit with a segmentaton fault. In conclusion, when
--fg-scenery points to a non-existing directory, FlightGear seg faults.
[...]
Could this be related to the terrain/object separation sup
* Curtis L. Olson -- Monday 17 January 2005 21:36:
> >As a result, FlightGear quit with a segmentaton fault. In conclusion, when
> >--fg-scenery points to a non-existing directory, FlightGear seg faults.
[...]
> Could this be related to the terrain/object separation support in the
> newest versi
