Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!uakari.primate.wisc.edu!ames!lll-winken!uunet!odi!ed From: ed@odi.com (Ed Schwalenberg) Newsgroups: comp.windows.ms.programmer Subject: Re: WDEB386 Message-ID: <1990Dec1.203147.15307@odi.com> Date: 1 Dec 90 20:31:47 GMT References: Organization: Object Design, Inc. Lines: 31 In-Reply-To: gmurray@compulink.co.uk's message of 30 Nov 90 21:46:00 GMT In article Graham Murray writes: I have a serial terminal connected, running the debugging version of windows. I am starting WDEB386 with the following command line from \windows\system directory: WDEB386 /C:2 /V /S:krnl386.sym /S:user.sym /S:gdi.sym ..\win.com /3 This starts Windows and displays all the segment addresses as they load. However, at no time am I given ANY prompt to enter commands. You can do one of these things, which are documented in the DDK, 17.6.1: 1. Type CTRL+ALT+SYSRQ on the PC keyboard at any time. This will invoke a breakpoint, and you will be able to talk to WDEB386 on the serial terminal. 2. Put breakpoint instructions (INT 1 or INT 3) in your code. INT 1's will stop after the INT, INT 3's will stop "before" the INT 3. In either case, continuing with "g" or "t" or "p" will work. 3. Generate an NMI. 4. Use the "/b" command-line flag to WDEB386, which will enter the debugger when Windows is halfway through initialization. If I press ctrl+C when Windows is idle, nothing happens. If I press it when the segment adresses are being displayed, it always stops at the same CS:EIP at 28:xxx. On typing G or any other command that I think should cause Windows to continue executing, the computer just re-boots! Don't do that, then. Use ^S^Q to stop and start WDEB386 typeout; use one of the methods above to enter the debugger. The documentation in Tools is awful. If you have the DDK, be sure to run the version of WIN386.EXE that comes with it. It has lots of nifty debugging features, some of which are obviously helpful and others which are tantamount to an ADVENTURE game.