Jon Berndt wrote:
I'm continuing to install the new JSBSim code. I've run into a strange problem.
After I
start up FlightGear and begin to parse an aircraft, I'll be humming along just
fine
until
I get to the point where the engine file is specified. When the engine file is
specified,
it causes the file to be opened and read using a call to the easyXML routine,
readXML().
It's the same routine, of course, that is being used to successfully parse the
main
aircraft config file. This works fine in JSBSim standalone, but in FlightGear,
when this
second call to readXML() is made, the program dies:
FlightGear aborting
I'm wondering if I missed something in the build process?
Are you calling readXML while another call to readXML is in progress? It
could be (I haven't checked this yet) that this function uses static
local variables to store information and calling it again while another
call is in progress would destroy the stored values.
It might be better to store the filenames that need to be read and read
them one after another.
Erik
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
