Difference between revisions of "Tracefile"
From GnuCash
(text about trace file) |
m (reporting a bug) |
||
| (18 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | ;Error Messages: and optionally more details are usually during a ''GnuCash session'' collected in a ''trace file''. The content of this file is very important when [[Bugzilla|reporting a bug]]. | |
| + | :;For Crashs of the Program: also a [[Stack Trace]] is desired. | ||
| − | At | + | ;At Each Program Start: a new trace file will be created and all configured output during the program run will be appended to that file. See [[Logging]] to fine tune the capabilities and save your settings in a configuration file. |
| + | :;Linux and {{Mac}} users: want to save a copy ''before the next GnuCash start'' if the file contains relevant infos. | ||
| − | + | ;Third party components: have their own log facilities. If you use [[AqBanking]], you might also wish to read about [[AqBanking#Debugging|AqBanking Debugging]]. | |
| + | [[Category:Log]] | ||
| − | If you experience | + | == Name and Location == |
| + | === Linux, *BSD etc. === | ||
| + | On ''Linux'', the most recent <tt>gnucash.trace</tt> file is located in <tt>/tmp</tt>. ''Some BSD variants'' use <tt>/var/tmp</tt> instead. | ||
| + | * Rename or move it as you like to safeguard it against overwriting. | ||
| + | |||
| + | === {{Mac}} === | ||
| + | On {{Mac}}, Gnucash creates the tracefile, gnucash.trace, in the operating system's current temp folder, located in <tt>/var/folders</tt>. The rest of the path has the form <tt>yy/yy_lots_more_hex_characters/-Tmp-/gnucash.trace</tt>. Most systems have several of these, so the easiest thing to do ''on older systems'' is to open <tt>Terminal</tt> and run <syntaxhighlight lang="sh"> | ||
| + | find /var/folders -name gnucash.trace | ||
| + | </syntaxhighlight> and it will print out the path for you. | ||
| + | |||
| + | ;MacOS 10.13 (High Sierra): has added a convenience environment variable <tt>TMPDIR</tt> so if you have that or later you can easily find the tracefile with <tt>$TMPDIR/gnucash.trace</tt> | ||
| + | |||
| + | === Windows === | ||
| + | On [[Windows]] these files are named <tt>gnucash.trace.ABCDEF</tt>, where the .ABCDEF suffix is changed randomly on each start of gnucash. They are usually located in the folder | ||
| + | :;Since Vista: <tt>C:\Users\myname\AppData\Local\Temp</tt> | ||
| + | :;Windows XP: <tt>C:\Documents and Settings\myname\Local Settings\Temp</tt> | ||
| + | :for a user named <q>myname</q>. | ||
| + | ;Notes: | ||
| + | :*The folder name <tt>Local Settings</tt> might be named differently in your native ''language'' like in German <tt>Anwendungsdaten</tt>. | ||
| + | :*Windows Explorer ''hide''s the <tt>AppData</tt> directory, so after opening <tt>c:\Users\myname</tt> click in the path bar at the top and type "\AppData" and press return. The AppData folder will open and you can continue to navigate normally. | ||
| + | :*It might also be a ''hidden system folder'' which is shown only if you change the folder properties to <tt>Not hide system files/folders</tt> in your file manager like <tt>Windows Explorer</tt>. | ||
| + | :*If you set the Windows ''environment variables'' <tt>TMPDIR</tt>, <tt>TMP</tt>, or <tt>TEMP</tt> – in DOS mode use the <tt>SET</tt> command – this location may change. | ||
| + | |||
| + | If you experience unexpected behavior or crashes, check the latest of these files (or the one created when the problem started) and add all interesting-looking lines of that file to your error reports (e.g. in [[Bugzilla]]). Please include at least the lines with the keywords <tt>WARN</tt> (for warning) and <tt>CRIT</tt> (for critical warning). | ||
Latest revision as of 00:42, 20 March 2024
- Error Messages
- and optionally more details are usually during a GnuCash session collected in a trace file. The content of this file is very important when reporting a bug.
- For Crashs of the Program
- also a Stack Trace is desired.
- At Each Program Start
- a new trace file will be created and all configured output during the program run will be appended to that file. See Logging to fine tune the capabilities and save your settings in a configuration file.
- Linux and macOS users
- want to save a copy before the next GnuCash start if the file contains relevant infos.
- Third party components
- have their own log facilities. If you use AqBanking, you might also wish to read about AqBanking Debugging.
Name and Location
Linux, *BSD etc.
On Linux, the most recent gnucash.trace file is located in /tmp. Some BSD variants use /var/tmp instead.
- Rename or move it as you like to safeguard it against overwriting.
macOS
On macOS, Gnucash creates the tracefile, gnucash.trace, in the operating system's current temp folder, located in /var/folders. The rest of the path has the form yy/yy_lots_more_hex_characters/-Tmp-/gnucash.trace. Most systems have several of these, so the easiest thing to do on older systems is to open Terminal and runfind /var/folders -name gnucash.trace
- MacOS 10.13 (High Sierra)
- has added a convenience environment variable TMPDIR so if you have that or later you can easily find the tracefile with $TMPDIR/gnucash.trace
Windows
On Windows these files are named gnucash.trace.ABCDEF, where the .ABCDEF suffix is changed randomly on each start of gnucash. They are usually located in the folder
- Since Vista
- C:\Users\myname\AppData\Local\Temp
- Windows XP
- C:\Documents and Settings\myname\Local Settings\Temp
- for a user named
myname
. - Notes
-
- The folder name Local Settings might be named differently in your native language like in German Anwendungsdaten.
- Windows Explorer hides the AppData directory, so after opening c:\Users\myname click in the path bar at the top and type "\AppData" and press return. The AppData folder will open and you can continue to navigate normally.
- It might also be a hidden system folder which is shown only if you change the folder properties to Not hide system files/folders in your file manager like Windows Explorer.
- If you set the Windows environment variables TMPDIR, TMP, or TEMP – in DOS mode use the SET command – this location may change.
If you experience unexpected behavior or crashes, check the latest of these files (or the one created when the problem started) and add all interesting-looking lines of that file to your error reports (e.g. in Bugzilla). Please include at least the lines with the keywords WARN (for warning) and CRIT (for critical warning).
