Originally created by: gijsrooy
Originally owned by: gijsrooy
What steps will reproduce the problem?
1. Load a JSBSim aircraft (eg. C172P) at any airport (for example EHLE).
2. Through the Location> Location on ground dialog, select another airport (eg. EHAL).
What is the expected output? What do you see instead?
FlightGear aborts with the following console message:
Tried to initialize a non-existent engine!
Aircraft propulsion element has problems in file D:/FlightGear/data/Aircraft/c172p/c172p.xml
Unknown exception in the main loop. Aborting...
Possible cause: No such file or directory
What version (or GIT date / Hudson build number)?
Git from December 6 with Hudson build #78 (http://flightgear.simpits.org:8080/job/Win32-installer/78/)
What operating system and graphics card?
Window Vista, NVIDIA Geforce Go 7300
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
Here is the output with --log-level=info: http://pastebin.ca/2017425
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Output also as attachment now (in case we can't fix this in a few days and pastebin expires :) ).
Labels: FDM
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: ahve... (code.google.com)@gmail.com
Same results in Dec 12 git. Gdb backtrace: http://pastebin.com/WnhAcxqG
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Cc: and...@gidenstam.org
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
Just for my memory:
#0 0x91a1a259 in __cxa_throw ()
#1 0x005b81b3 in JSBSim::FGPropulsion::InitRunning (this=0x447daea0, n=0) at /Users/jmt/Code/Macflightgear/flightgear/flightgear/src/FDM/JSBSim/models/FGPropulsion.cpp:244
#2 0x005ba175 in SGRawValueMethods<JSBSim::FGPropulsion, int>::setValue (this=0x1a8a1580, value=0) at props.hxx:579
#3 0x0003f8a0 in SGPropertyNode::set_int () at FGTrimAxis.h:70
#4 0x006560f3 in SGPropertyNode::setIntValue () at locale_facets.tcc:2578
#5 0x00223df8 in setValue (node=0x1a851370, value=0) at props.hxx:1743
#6 0x0065f7be in SGPropertyNode::setValue<int> () at locale_facets.tcc:2578
#7 0x0065f899 in SGPropertyNode::tie<int> () at locale_facets.tcc:2578
#8 0x0065636e in SGPropertyNode::tie () at locale_facets.tcc:2578
#9 0x005ba431 in JSBSim::FGPropertyManager::Tie<JSBSim::FGPropulsion, int> (this=0x2be4490, name=@0xbfffe33c, obj=0x447daea0, getter={__pfn = 0, __delta = 0}, setter={__pfn = 0x5b811e <JSBSim::FGPropulsion::InitRunning(int)>, __delta = 0}, useDefault=true) at FGPropertyManager.h:585
#10 0x005b49f1 in JSBSim::FGPropulsion::bind (this=0x447daea0) at /Users/jmt/Code/Macflightgear/flightgear/flightgear/src/FDM/JSBSim/models/FGPropulsion.cpp:649
#11 0x005b74fd in JSBSim::FGPropulsion::Load (this=0x447daea0, el=0x1a86c940) at /Users/jmt/Code/Macflightgear/flightgear/flightgear/src/FDM/JSBSim/models/FGPropulsion.cpp:310
#12 0x004ab314 in JSBSim::FGFDMExec::LoadModel (this=0x1a822a30, model=@0xbfffe790, addModelToPath=false) at /Users/jmt/Code/Macflightgear/flightgear/flightgear/src/FDM/JSBSim/FGFDMExec.cpp:586
#13 0x004ac676 in JSBSim::FGFDMExec::LoadModel (this=0x1a822a30, AircraftPath=@0xbfffe784, EnginePath=@0xbfffe788, SystemsPath=@0xbfffe78c, model=@0xbfffe790, addModelToPath=false) at /Users/jmt/Code/Macflightgear/flightgear/flightgear/src/FDM/JSBSim/FGFDMExec.cpp:473
#14 0x004bc2f1 in FGJSBsim::FGJSBsim (this=0x22230c00, dt=0.0083333333333333332) at /Users/jmt/Code/Macflightgear/flightgear/flightgear/src/FDM/JSBSim/JSBSim.cxx:185
#15 0x003f1fe6 in FDMShell::createImplementation (this=0x20f32010) at /Users/jmt/Code/Macflightgear/flightgear/flightgear/src/FDM/fdm_shell.cxx:190
#16 0x003f2dfc in FDMShell::init (this=0x20f32010) at /Users/jmt/Code/Macflightgear/flightgear/flightgear/src/FDM/fdm_shell.cxx:73
#17 0x003f2dad in FDMShell::reinit (this=0x20f32010) at /Users/jmt/Code/Macflightgear/flightgear/flightgear/src/FDM/fdm_shell.cxx:86
#18 0x00098c41 in fgReInitSubsystems () at /Users/jmt/Code/Macflightgear/flightgear/flightgear/src/Main/fg_init.cxx:1560
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: anders.g... (code.google.com)@gmail.com
(No comment was entered for this change.)
Cc: -and...@gidenstam.org
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
Issue 216 has been merged into this issue.
Related
Tickets:
#216View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
Note I just filed bug 222 to track the long-standing JSBsim NaN-on-reset bug, which is currently masked by this issue.
Related
Tickets:
#222View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
Figured this one out, partially - the problem is the useDefault behaviour of SGPropertyNode::tie, which is different if there's an existing value or not, for the property. If there is an existing value for the property, useDefault is true, and hence we run the setters prematurely, which JSBSim seems unprepared to accept.
I'm going to investigate removing (deleting) all properties below /fdm/jsbim when we re-init, in the JSBSim interface. Brutal, but probably effective.
Status: Accepted
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
Fixed by http://gitorious.org/fg/flightgear/commit/6fd33dd2c38d02a017399c6cc67639e801b3509a
This also seems to help with bug 222, locally, but needs much more testing to confirm or deny that.
Status: Fixed
Related
Tickets:
#222View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: g...@av8n.com
This is not what I would call fixed. The behavior is changed in the
sense that I no longer observe an "unknown exception" ... instead I
observe a segmentation fault ... which is not an improvement.
I tried the Location (on ground) feature several times with the
same result.
Status: Testing
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
Pushed a more specific fix for this, to FG - needs to be merged to JSBSim CVS at some point, following discussion with them.
http://gitorious.org/fg/flightgear/commit/d4d70200eb635318aa4b9fd700ac4a9310899426
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Status: Fixed
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
Yeaah, fixed!
Thanks James!
Status: Verified
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Temp
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Verified