i did try using "$FG_HOME/Export/fg_log.csv" but the $FG_HOME macro is not expanded and the defect is triggered as well.įor now, the easiest thing to do is to specify a proper path that FG can write the desired output file to. Avoiding overflight of Ukrainian and/or Russian airspace: The route generator in the advanced Flight Planner can be instructed to avoid one or more FIRs by. If i specify a proper and writable path to the output file as given in the error output (/home/myuser/.fgfs/Export/fg_log.csv), there is no problem, no crash, and a proper csv file is written in the specified directory. ![]() SIGSEGV when attempting to use F10->Debug->Logging with unwritable output path i have backtraces for the crashing scenario and will forward them to the mailing list for analysis and remediation. The segmentation fault happens afterward when a shutdown appears to be automatically triggered. Please choose another location, for instance in the $FG_HOME/Export folder (/home/myuser/.fgfs/Export). When i attempt the same as you describe, i see the following logged in the console and in the fgfs.log file.Ĭode: Select all 55.96 :general The FGLogger logging system, via the '/logging/log/filename' property, was asked to write to 'fg_log.csv', however this path is not authorized for writing anymore for security reasons. I think you can tell FG that certain directories are allowed to be written to but i'm unable to easily find this information in the wiki and my google-fu seems to be off this morning Re: custom logging output file / fix for CVE-2017-13709 ![]() ![]() The file writing security was adjusted back in 2017.3.1 to avoid CVE-2017-13709.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |