185
edits
Commonly used debugging tools: Difference between revisions
Jump to navigation
Jump to search
→Finding fgfs.log: removed the line saying to navigate to $FG_HOME since the full path is already given in the locations...
(Created page with "There are some relatively simple but '''commonly used debugging tools''' that might answer questions of for example why your installation of FlightGear will not run properly o...") |
(→Finding fgfs.log: removed the line saying to navigate to $FG_HOME since the full path is already given in the locations...) |
||
| (10 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{stub}} | |||
There are some relatively simple but '''commonly used debugging tools''' that might answer questions of for example why your installation of FlightGear will not run properly or at all, why an aircraft might have problems or why flying in a certain area always cause FlightGear crashes. | There are some relatively simple but '''commonly used debugging tools''' that might answer questions of for example why your installation of FlightGear will not run properly or at all, why an aircraft might have problems or why flying in a certain area always cause FlightGear crashes. | ||
| Line 18: | Line 21: | ||
=== Setting the debug level === | === Setting the debug level === | ||
==== FGRun ==== | ==== FGRun ==== | ||
In FGRun go to the last page click {{key press|Advanced...}} then, in the list to the left, click "Debug" and chose the desired debug level. | In FGRun go to the last page click {{key press|Advanced...}} then, in the list to the left, click "Debug" and then chose the desired debug level in the list. | ||
==== Command line ==== | ==== Command line ==== | ||
Add <code>-log-level ''debug level''</code> to your command line. | {{note|Debug levels must be lowercase. For example <code>debug</code>, not <code><s> Debug </s></code>.}} | ||
Add <code>--log-level=''debug level''</code> to your command line. | |||
== The console window == | == The console window == | ||
| Line 28: | Line 33: | ||
== fgfs.log == | == fgfs.log == | ||
The startup log file contains nearly the same information that is output on the console. | The startup log file contains nearly the same information that is output on the console. | ||
The goal of adding the log file was to capture some debugging output in a way that is robust for users, i.e just works, and works ‘historically’, i.e is useful when a problem occurs since it was already enabled. The level is fixed at INFO because a lower level wouldn’t contain enough detail for debugging, but a higher level (SG_DEBUG) the files would be huge for a long FG session. This is my decision of course and it can be changed if people are happy with 100MB+ text files in their FG_HOME. Or we add a new option to set the file-log-level, but again the intention was for this feature to be as automatic as possible.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35144644/ | |||
|title = <nowiki> Re: [Flightgear-devel] fgfs.log </nowiki> | |||
|author = <nowiki> James Turner </nowiki> | |||
|date = Jun 8th, 2016 | |||
|added = Jun 8th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
=== Finding fgfs.log === | === Finding fgfs.log === | ||
; Mac: <code>~/Library/Application Support/FlightGear/fgfs.log</code> | ; Mac: <code>~/Library/Application Support/FlightGear/fgfs.log</code> | ||
; Windows: <code>C:\Users\''user name''\AppData\Roaming\flightgear.org\fgfs.log</code> | ; Windows: <code>C:\Users\''user name''\AppData\Roaming\flightgear.org\fgfs.log</code> | ||
; Linux: <code>~/.fgfs/fgfs.log</code> | |||
== The property browser == | == The property browser == | ||