> To: [EMAIL PROTECTED] > From: "Arkady V.Belousov" <[EMAIL PROTECTED]> > Subject: Re: [Freedos-devel] debug 0.95f and 0.98 'Unexpected single-step > interrupt' > Date: Tue, 4 May 2004 15:42:29 +0400 (MSD) > > Hi! > > Try this: > > ______________O\_/_________________________________\_/O______________ > debug > a > mov ah,4c > int 21 > int 3 > > g=100 > g > _____________________________________________________________________ > O/~\ /~\O
OK, I've tried it. Under MS-DOS 2.1 with native DEBUG and Win XP with native DEBUG, it drops you out of DEBUG and back into COMMAND.COM. In a way this makes sense, since the above code terminates a program and since you haven't loaded a program into DEBUG the only program that DOS (or XP) could possibly terminate is DEBUG itself. Under MS-DOS 2.1 with fd-debug, you're back at the DEBUG prompt. Under dosemu 1.2.1 and FreeDOS (I don't know what FD version, sorry, but kernel.sys was dated 31 January 2004), I get "Unexpected single-step interrupt". So. Are you saying that the behavior under MS-DOS 2.1 is buggy? I strongly suspect that the buggy behavior under FreeDOS is either the problem of dosemu or freedos. --Paul Vojta, [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
