I have an answer to the Open Watcom (OW) integration problem but I need to talk to people who know something about that part of the system, and can suggest who can make what are probably minor changes. It looks to be beyond me.
Core OW development is ongoing with the next version in early beta, particularly changes to the C++ compiler.
After a lot of looking and reading I reached the conclusion that whilst OW mentions DWARF 2 for debug format, with Win32 PE executables this is incompatible with GDB. Linux might not be (OW is cross platform) to be investigated.
Other people have tried to get GDB working in C::B with OW, no dice.
The answer is very simple. OW has two debugger front ends, character windows or Windows, including remote debug to other platforms from DOS to OS/2
It is as trival as adding one as a tool in C::B, is no bad reflection on the work done on C::B is just that for this toolchain we use an external. Anyone wants to try a proof of concept, here is the magic
Tool name: OW Debugger
Executable: C:\watcom\binnt\wdw.exe (adjust as required, works with release 1.7a and beta 1.8 )
Parameters: $(TARGET_OUTPUT_FILE)
And check "Launch tool hidden ..." (second from top)
That basically works assuming the compiler and linker flags are set right.
debug all
Plus the following for a separate symbol file.
op symf
How can the configured command line for a run be passed across? Needs another $ variable
Similarly the OW Profiler can be invoked and the Profile viewer. (can use $(TARGET_OUTPUT_BASENAME).smp)
Various things are not quite right, needs extra info passed across.
If this route is taken to fixing the OW configuration it needs some other changes and the default install setting up.
Anyone interested please contact me. There is more going on, I hope good things, which I do not mention here.
