Quote:
Originally Posted by darencainiao
Is it using Qt's qDebug() function?
|
For quick stuff on Windows, yes. There's already a lot of debug information that that can output to a file (by putting a user-writable file path in the SIGIL_DEBUG_LOGFILE environment variable) and by setting any of the #define DBG if(0) directives found at the top of many files to #define DBG if(1). Any qDebug() statements you add will also be output to the log file defined by SIGIL_DEBUG_LOGFILE.
Quote:
Originally Posted by darencainiao
As far as I know, references to classes in C++ is somewhat confusing, and it will be difficult to debug and find bug without step through in Visual Studio's IDE.
|
I personally find Visual Studio's IDE/debugger to be terribly confusing, bloated and nearly unusable. Plus, you need a Microsoft account to even
open the IDE. So I don't use it.
Quote:
Originally Posted by darencainiao
By the way, would it be better to debug sigil in Linux?
|
For any kind breakpoint or backtrace work, yes. At least I find it to be better, anyway. Almost all of my development work on Sigil is done on Linux. I typically find that bugs/crashes in Windows Sigil will often be duplicated in Linux Sigil. The command-line debugging tools of Linux are infinitely more familiar/intuitive/simple for me.
Another part of the problem is that Sigil on Windows will not run from its build location without a lot of extra wrangling. It needs to be
installed because of its bundled Python dependencies. So running Sigil with the debugger and stepping in/out/through are problematic. Heck, just building a debug version of Sigil is difficult on Windows because of the embedded Python portions. It wants a debug version of Python as well.