Note that I am trying to debug on Windows, not on Linux.
The executable created with gcc is a regular win32 PE executable, thar
requires a gcc library dll, and msvcrt.dll
I read somewhere that SciTech people debug all gcc applications with wdw,
because it is a much better debugger than gdb and its GUIs (CodeBlocks,
they say "Open Watcom now includes GCC and PowerPC debugging support, so we
do all our debugging is done with Open Watcom".
And this was in 2006.
Post by Wilton Helm
Someone else might know more details. I see both possibilities and
problems. Some of the problems are related to the fact that the other
compilers probably use different calling conventions that OW, but OW
supports a wide variety of calling conventions, so that should be
solvable. The problem might be how to pass that information to the
debugger, as I think it normally gets it from the files. In a similar
vein, C++ name mangling, etc. can vary a lot from compiler to compiler, as
well as RTL calls. Also, OW doesn't support .dll libraries on Linux,
which might raise some problems for gcc.
What you are describing seems to primarily relate to how it acquires the
source code. The program also has to compile the object files with
debugging information, including line number references, in them (and
passed through the linker into the executable) or in a .sym file--in a
format OW can recognize. Otherwise it doesn't know where to look in the
source files. Again, OW supports multiple formats for this information, so
it is possible it could be convinced how to find it.