Commonly used debugging tools: Difference between revisions

Jump to navigation Jump to search
(→‎Finding fgfs.log: Updated the Linux path to match the Mac and Windows paths.)
Line 33: 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 ===

Navigation menu