(→Memory Values) |
|||
Line 56: | Line 56: | ||
* 0xCCCCCCCC - Allocated on stack, but not initialized | * 0xCCCCCCCC - Allocated on stack, but not initialized | ||
See also: [http://www.samblackburn.com/wfc/technotes/WTN006.htm] | See also: [http://www.samblackburn.com/wfc/technotes/WTN006.htm] | ||
− | ==How to Not Step Into Functions in the Debugger | + | |
+ | ==How to Not Step Into Functions in the Debugger== | ||
You'll probably want to avoind stepping into lower-level functions like QString constructors or operators. Here's the detailed (unofficial) [http://blogs.msdn.com/andypennell/archive/2004/02/06/69004.aspx instruction] for various msvc versions. | You'll probably want to avoind stepping into lower-level functions like QString constructors or operators. Here's the detailed (unofficial) [http://blogs.msdn.com/andypennell/archive/2004/02/06/69004.aspx instruction] for various msvc versions. | ||
Debug messages (logs) generated by kDebug() and kWarning() are not visible on MS Windows unless application is compiled in so-called CONSOLE subsystem. To show these messages also in WINDOWS subsystem, you can use DebugView tool, coming from SysInternals (currently acquired by Microsoft). The tool offers searching in logs, filtering and saving them to file.
kioslaves on windows are started by klauncher (or kio) as separate kioslave processes. The kioslave executable then loads the related kioslave dll dynamically.
To debug kioslaves set the KDE_SLAVE_DEBUG_WAIT environment variable to the name of the kioslave to debug (for example 'file' for the kio_file slave) and restart klauncher. If the requested kioslave is requested the next time, a debugger will be started and attached to the kioslave process immediatly before the kio_slave 'kdemain' function.
On mingw platform gdb is launched and connected to the kioslave process, on msvc platforms the currently install just-in-time-debugger is used. This may be msvc vc2005 ide or the windbg debugger [1]. The latter could be set as jit-debugger by running windbg -I.
You may inspect kioslave sources [2] for more informations.
Let's assume you're using command line tools (typically SCons) and want to use MS Visual Studio environment for just debugging. You don't need to create msvc project for your KDE application to be able to start debugging.
If you have your application is already running, you can attach to it and then start debugging.
You can create a macro that automates the task. See [3].
If you are using the debug heap, memory is initialized and cleared with special values. Most interesting values are:
See also: [4]
You'll probably want to avoind stepping into lower-level functions like QString constructors or operators. Here's the detailed (unofficial) instruction for various msvc versions.