debug log

[TuxedoHam]

klog 2.0-1 under Linux is writing a debug log file in ~/.klog/ even though it set to "DebugLog=False;" in the config file and the app does not have the check box ticked

[ikbenkous]

I can confirm that this happens here. klog creates an empty file in ~/.klog/klogdebug.log. I don't know whether this would be classified as a bug or feature. But it's certainly interesting.

What do you think should happen? @TuxedoHam No file created at all?

[TuxedoHam]

I can confirm that this happens here. klog creates an empty file in ~/.klog/klogdebug.log. I don't know whether this would be classified as a bug or feature. But it's certainly interesting.

What do you think should happen? @TuxedoHam No file created at all?

@ikbenkous Well their is a couple options I can see that you can go about this

1. Don't create a debug log what so ever unless it is selected in in the GUI and then when you quit the program it writes out with filename eg time-date_klogdebug.log
2. Hide the debug option in the GUI but have it that the debug is run like klog --debug and it writes out to log file named like above and write out when the program is quit either via the GUI or CTRL + C in Linux terminal example.
3. I guess you can just leave all the debugging done in the IDE as the developer(s) writing the code.

Option 2 might be the better option due all the different versions of OS's that are around theses days.

[ikbenkous]

~/.klog/klogdebug.log is not what it seems! This file is an ADIF. So either we're both mistaken by the confusing terminology of "log"/"logger"/"logging", or klog is doing something REALLY wrong by saving an ADIF to a log file??

"log" confusion

When showing the word "log" in the UI, there needs to be clear disambiguation as to what kind of log. ('Ham log' or 'Debug log'). Even if it's clear what is meant by the context in which the "log" word is used, the user might miss the context, read over it in haste and have a headache. It can't hurt to be explicit/pedantic and it's probably better to be explicit.

Additionally, the UI says this: (Hard to read, I know). It says: Select to use the following name for the logfile without being asked for it again.

What kind of "log" is this? An error log or a ham log? No idea.

Regarding your proposals

Only debugging in IDE is a really bad idea. End-users don't have debug symbols, source code, IDEs, skills, time or patience to debug as a developer. Error logging is vital to figure out what happens as an end-user. Also: log buffers should be flushed every time it's written to. Because if the program crashes before it flushes it out, you can't know what happened right before it crashed.

I'm not fond of spamming "time-date_debug.log" files unless:

1. They're inside a directory in ~/.klog/debug/
2. Stale log files older than 3 months are automatically deleted/rotated.
3. You can disable automatic deletion/rotation and enable 'spamming log files'

This entire issue has got me a little confused. haha

[TuxedoHam]

@ikbenkous This is what my Misc tab looks like and my QSO's are being logged to a ADI file

The ADI file is what I have used from first ever starting to use KLog, so that was/is default file to log QSO to.

As for the klogdebug.log seems to be created every time klog is run and the file size is 0 byte.

Regards to the debug log file, they where 3 option I see that can be be taken, yeah the time-date_debug.log could get little noisy if you forget to turn off debugging when finished with it. When the developer goes through the IDE debugging processes has way more info to what is going on with your program, and also the program when compiled at the end with debug internally turned off the end program is a lot smaller. Also some error in debug can be rather frustrating to work due to nonsensical error output.

But at the end the day it all down to the developer(s) how they best see how they want to deal with debugging, I know some devs prefer to deal with debug themselves as it can be like pulling teeth to get the information needed when people put in a bug report.

You are you right can/is confusing, and this one reason you have Alpha and Beta version ;)