On Tue, 24 Feb 2004 [EMAIL PROTECTED] wrote: > b) How can I debug those programs from within WinNT? Both the tools in > BINNT and BINW complain about invalid debugging information. I pass the > "-d3" option to WCC.EXE and WLINK.EXE gets "DEBUG WATCOM ALL". The > executable has lots of stuff appended, looking like debug infos.
not sure here. You might try to narrow down though: first try: wcl -d1 hello.c wd hello.exe then: wcl -d2 hello.c wd hello.exe Also you might want to use "remote" debugging -- it's not really remote but it works the same way in that you regard the winnt dos box as a virtual machine: in a winnt dos box you type: vdmserv (hello.exe needs to be in the current directory) and you start binnt\wdw or binnt\wd using wdw /tr=vdm hello.exe (using start->run or another cmd.exe) wdw will now ask vdmserv to run/trace hello.exe. Bart ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
