One CAN set the departure runway, then the default SID first. Then set the arrival airport as the same airport, set the same runway and then set the default approach as a work around.
Hint from Tikibar. He said he thought it might be related to the bug that if the first waypoint is 0 then sim crash.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Although the method for reproducing this is different, this may a duplicate of https://sourceforge.net/p/flightgear/codetickets/1703/ because the top five frames of the backtrace are the same in both cases. Even if it's not a strict duplicate, it appears to be closely related.
Here's the backtrace using the method described in this bug (#1757):
Program received signal SIGSEGV, Segmentation fault.
---Type <return> to continue, or q <return> to quit---
0x0000000000936803 in computeLegCourse (radiusM=1473.7747730309509,
previous=..., this=0xff08ac0)
at /home/richard/Flightgear/flightgear/src/Navaids/routePath.cxx:247
247 if (wpt->type() == "hold") {
(gdb) bt
#0 0x0000000000936803 in computeLegCourse (radiusM=1473.7747730309509,
previous=..., this=0xff08ac0)
at /home/richard/Flightgear/flightgear/src/Navaids/routePath.cxx:247
#1 RoutePath::commonInit (this=this@entry=0x7fffffffcaf0)
at /home/richard/Flightgear/flightgear/src/Navaids/routePath.cxx:904
#2 0x0000000000937aa6 in RoutePath::RoutePath (this=0x7fffffffcaf0,
fp=0xe026980)
at /home/richard/Flightgear/flightgear/src/Navaids/routePath.cxx:862
#3 0x00000000009468a9 in flightgear::FlightPlan::rebuildLegData (
this=this@entry=0xe026980)
at /home/richard/Flightgear/flightgear/src/Navaids/FlightPlan.cxx:1207
#4 0x000000000094855c in unlockDelegate (this=0xe026980)
at /home/richard/Flightgear/flightgear/src/Navaids/FlightPlan.cxx:1265
#5 flightgear::FlightPlan::setDestination (this=0xe026980, rwy=0x1873710)
at /home/richard/Flightgear/flightgear/src/Navaids/FlightPlan.cxx:530
#6 0x00000000007340a3 in FGRouteMgr::setDestinationRunway (this=0x19eebd0,
aIdent=0x10284840 "34L")
at /home/richard/Flightgear/flightgear/src/Autopilot/route_mgr.cxx:998
#7 0x000000000073a58f in SGRawValueMethods<FGRouteMgr, char const*>::setValue
(this=<optimised out>, value=<optimised out>)
at /home/richard/Flightgear/install/include/simgear/props/props.hxx:562
#8 0x00007ffff6b96ff2 in SGPropertyNode::set_string (this=0x1955180,
val=0x10284840 "34L")
at /home/richard/Flightgear/simgear/simgear/props/props.cxx:502
#9 0x00007ffff6b9386d in SGPropertyNode::setStringValue (
this=this@entry=0x1955180, value=0x10284840 "34L")
at /home/richard/Flightgear/simgear/simgear/props/props.cxx:1553
#10 0x00000000007ab399 in copy_from_pui (node=<optimised out>,
object=0x102845e8)
at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:647
#11 FGPUIDialog::applyValues (this=this@entry=0x100ffaa0, objectName=...)
at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:750
#12 0x000000000062f19f in do_dialog_apply (arg=0x10285200)
at /home/richard/Flightgear/flightgear/src/Main/fg_commands.cxx:1007
#13 0x00007ffff6bac1db in SGBinding::innerFire (this=0x10285390)
at /home/richard/Flightgear/simgear/simgear/structure/SGBinding.cxx:92
#14 0x00007ffff6bacef9 in SGBinding::fire (this=<optimised out>)
at /home/richard/Flightgear/simgear/simgear/structure/SGBinding.cxx:79
#15 0x00000000007ab0b7 in action_callback (object=<optimised out>)
at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:563
#16 0x00007ffff4bb7bc9 in puOneShot::doHit(int, int, int, int) ()
from /usr/lib/libplibpu.so.1
#17 0x00007ffff4bb73ad in puObject::checkHit(int, int, int, int) ()
from /usr/lib/libplibpu.so.1
#18 0x00007ffff4bb80be in puPopupMenu::checkHit(int, int, int, int) ()
from /usr/lib/libplibpu.so.1
#19 0x00007ffff4bb3f37 in puGroup::checkHit(int, int, int, int) ()
from /usr/lib/libplibpu.so.1
#20 0x00000000007ab104 in fgComboBox::checkHit (this=0x102845d0,
b=<optimised out>, up=<optimised out>, x=<optimised out>,
y=<optimised out>)
at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:1578
#21 0x00007ffff4bb3f37 in puGroup::checkHit(int, int, int, int) ()
from /usr/lib/libplibpu.so.1
#22 0x00007ffff4bb3f37 in puGroup::checkHit(int, int, int, int) ()
from /usr/lib/libplibpu.so.1
#23 0x00000000007ad7dd in fgPopup::checkHit (this=0x1027c070,
button=<optimised out>, updown=1, x=970, y=941)
at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:314
#24 0x00007ffff4bb3f37 in puGroup::checkHit(int, int, int, int) ()
from /usr/lib/libplibpu.so.1
#25 0x00007ffff4bb1084 in puMouse(int, int, int, int) ()
from /usr/lib/libplibpu.so.1
#26 0x00000000007fa66c in FGMouseInput::doMouseClick (this=0x1a19960,
b=b@entry=0, updown=1, x=x@entry=970, y=y@entry=139,
mainWindow=mainWindow@entry=true, ea=ea@entry=0xff39020)
at /home/richard/Flightgear/flightgear/src/Input/FGMouseInput.cxx:604
#27 0x00000000007fa739 in mouseClickHandler (button=button@entry=0,
updown=<optimised out>, x=x@entry=970, y=y@entry=139,
mainWindow=mainWindow@entry=true, ea=ea@entry=0xff39020)
at /home/richard/Flightgear/flightgear/src/Input/FGMouseInput.cxx:357
#28 0x0000000000bca73e in flightgear::FGEventHandler::handle (
this=<optimised out>, ea=..., us=...)
at /home/richard/Flightgear/flightgear/src/Viewer/FGEventHandler.cxx:242
#29 0x00007ffff5eff737 in osgViewer::Viewer::eventTraversal() ()
from /usr/lib/libosgViewer.so.99
#30 0x00007ffff5f00ed9 in osgViewer::ViewerBase::frame(double) ()
from /usr/lib/libosgViewer.so.99
#31 0x0000000000bd05aa in fgOSMainLoop ()
at /home/richard/Flightgear/flightgear/src/Viewer/fg_os_osgviewer.cxx:335
#32 0x000000000065602f in fgMainInit (argc=21, argv=0x7fffffffdda8)
at /home/richard/Flightgear/flightgear/src/Main/main.cxx:506
#33 0x0000000000622846 in main (argc=21, argv=0x7fffffffdda8)
at /home/richard/Flightgear/flightgear/src/Main/bootstrap.cxx:234
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
situation still exists for 3.6 nightly FULL from july 21.
one can still do Departure airport, Departure Runway, Default sid, Arrival Airport, Arrival Runway, Default approach, and the sim doesn't immediately crash.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One CAN set the departure runway, then the default SID first. Then set the arrival airport as the same airport, set the same runway and then set the default approach as a work around.
Hint from Tikibar. He said he thought it might be related to the bug that if the first waypoint is 0 then sim crash.
Although the method for reproducing this is different, this may a duplicate of https://sourceforge.net/p/flightgear/codetickets/1703/ because the top five frames of the backtrace are the same in both cases. Even if it's not a strict duplicate, it appears to be closely related.
Here's the backtrace using the method described in this bug (#1757):
100% reproducable here.
Pinging James...
situation still exists for 3.6 nightly FULL from july 21.
one can still do Departure airport, Departure Runway, Default sid, Arrival Airport, Arrival Runway, Default approach, and the sim doesn't immediately crash.