search

open-watcom / open-watcom-v2

Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.
Other
959 stars 157 forks source link

Debug file format bugs with WDW.EXE (PM) debugger in OS/2 #672

Open zoomosis opened 3 years ago

zoomosis commented 3 years ago

Compiling source with "wcl386 -d2 -hw foo.c" then running "wdw foo.exe" results in OW 2.0's WDW not being able to find the foo.c source code. (where -hw = watcom debug format)

"wcl386 -d2 -hc foo.c" then "wdw foo.exe" causes WDW to crash on startup. (-hc = codeview debug format)

Similarly WD (the text mode debugger) also crashes on startup with the same binary. (Presumably WDW and WD share some code.)

So only "wcl386 -d2 -hd" works with WDW from OW 2.0.

These all seem to be problems in the WDW code in OW 2.0 and not WCL386 from OW2.0, because WDW 1.9 seems to work fine on OS/2 binaries produced by OW2.0's WCL386.

Thanks.

jmalak commented 3 years ago

Thanks for bug report. WDW and WD share the same code for all except User interface which contains 3-layers. Top layer AUI project which is common to WDW and WD. midle layer is GUI project which is different for graphical and character mode. low layer is UI project and is used only by character mode. Debug information processing is processed by DIP loadable module (one per each debug info format) is used by both WDW and WD, the same is for TRAP and MAD modules. The problem is probably in DIP module, bug specific for OS/2.

jmalak commented 3 years ago

Anyway OS/2 code is untested due to no interest from community.

zoomosis commented 3 years ago

Disappointing to hear about the OS/2 code, but understandable for a niche OS.

jmalak commented 3 years ago

It doesn't mean that OS/2 is not supported, only is untested due to limited resources and no interest from comunity. I have Virtual Machine with OS/2 installation for testing OW. I will look on your problems and fix them. Anyway character mode problems appeared on other OS-es too.

wwiv commented 1 year ago

F10 seems to be captured by the popup command in the sample.exe in bld\gui\sample for OS2 as well.

jmalak commented 1 year ago

Thanks for bug report. It is not only F10 also F8 etc. Menu works correctly, it looks like problem with macro file processing which doesn't change keyboard assignment.

wwiv commented 1 year ago

actually F8 was working for me, just F10. Same with the sample (turning on the status bar showed keys other than F10 being pressed). Was trying to debug but wdw and sample both crash when I hit breakpoints near that code

jmalak commented 1 year ago

It probably depends on what was done before. May be some memory corruption etc.

jmalak commented 1 year ago

As workaround you can use OW 1.9 debugger with OW 2.0 executable.