Tech. Note 1: Getting a debug trace

If you are having a problem with Guiffy, a debug trace may help us find the bug.

First, edit the guiffy.lax file to write stderr output to a file. The file guiffy.lax is located in the Guiffy install folder. Guiffy's default install paths are: NOTE: To replace the guiffy.lax file you will need to open the file as Administrator or SuperUser. Be sure once you're done and save the guiffy.lax file, the file is actually updated in the Guiffy install folder.

NOTE: Specify an absolute file path for the GDebug.txt file. Be sure you have write permission for the file path specified.

On Windows edit guiffy.lax, change the LAX.STDERR.REDIRECT line from:
lax.stderr.redirect=
An absolute path to your Documents folder for example would be something like:
lax.stderr.redirect=C:\\Users\\britcher\\My Documents\\GDebug.txt

On Linux edit guiffy.lax, change the LAX.STDERR.REDIRECT line from:
lax.stderr.redirect=
An absolute path to your Documents folder for example would be something like:
lax.stderr.redirect=/home/britcher/Documents/GDebug.txt

On MacOS edit guiffyCL.command.lax, change the LAX.STDERR.REDIRECT line from:
lax.stderr.redirect=console
An absolute path to your Documents folder for example would be something like:
lax.stderr.redirect=/Users/britcher/Documents/GDebug.txt
Then, on MacOS to run Guiffy with the debug trace enabled, execute guiffyCL.command.

Then, run Guiffy and reproduce your problem, and exit Guiffy. If the lax.stderr.redirect path is correct, the file GDebug.txt will be created and empty if it doesn't alreay exist. View the contents of the GDebug.txt file. If the GDebug.txt file has anything in it, include it with your problem report.

Documentation by Guiffy Software, Inc. 2018