Durk Talsma wrote:
> I'm cross posting this to the developers list, just in case somebody's
> inclined to do some bug fixing... :-)
>
> Yeah, that's exactly what I experienced yesterday, when I was testing out
a
> sample file for a reply to this list.
>
> B.t.w., It's not only the --flight-plan option, but also the --wp= option.
On
> the other hand, adding a way point while in flight seems to work still
>
> Just a random thought: The --flight-plan and --wp options related code is
> interacting heavily with the auto pilot code, so is there anything going
> wrong?
>
> Cheers,
> Durk
>
> >
> > I put three waypoints with altitudes in a textfile in the format:
> > [EMAIL PROTECTED]
> > [EMAIL PROTECTED]
> > [EMAIL PROTECTED]
> > when I issue "fgfs --flight-plan=test.plan" I had save the file as that
> > already) I get an immediate segfault.
In fact, --flight-plan and --wp are parsed before the Nav databases are
loaded.
The line :
result = globals->get_airports()->search( id );
in fgFindAirportID is dereferencing the NULL pointer returned by
globals->get_airports()
parse_flightplan and parse_wp ( parse_flightplan calls parse_wp ) should be
postponed after the call of fgInitNav but I don't know to do that for the
moment.
That's why adding WP after init time works.
-Fred
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
