20,741
edits
Howto:Reset/re-init Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Reset/re-init Troubleshooting (view source)
Revision as of 23:39, 21 November 2015
, 21 November 2015→Nasal example: has kinda become more than just an "example" meanwhile
m (→Nasal example: has kinda become more than just an "example" meanwhile) |
|||
| Line 198: | Line 198: | ||
{{Note|The subsystems shown in the table below seem to be fairly safe to remove/add at run-time, so that it would seem possible to come up with an extended minimal startup profile implemented in scripting space that will actually disable unneeded subsystems during startup.}} | {{Note|The subsystems shown in the table below seem to be fairly safe to remove/add at run-time, so that it would seem possible to come up with an extended minimal startup profile implemented in scripting space that will actually disable unneeded subsystems during startup.}} | ||
== Nasal | == Nasal dialog == | ||
{{Note|The following Nasal script can be executed via the Nasal Console or put in a separate file and executed via a menu item to easily test different aspects of reset/re-init. For the time being, you are likely to trigger segfaults/crashes or other undefined behavior (e.g., memory leaks), so it is recommended to run FlightGear in a GNU Debugger (GDB) session to obtain a backtrace. If you manage to cause a bug or crash, please file a bug report: {{Tickets}} }} | {{Note|The following Nasal script can be executed via the Nasal Console or put in a separate file and executed via a menu item to easily test different aspects of reset/re-init. For the time being, you are likely to trigger segfaults/crashes or other undefined behavior (e.g., memory leaks), so it is recommended to run FlightGear in a GNU Debugger (GDB) session to obtain a backtrace. If you manage to cause a bug or crash, please file a bug report: {{Tickets}} }} | ||