Re: how can I see the result of the program?
- From: NoSpam@xxxxxxxxxxx (Bob Masta)
- Date: Fri, 20 Oct 2006 12:27:21 GMT
On Thu, 19 Oct 2006 15:33:04 -0400, Frank Kotler
<spamtrap@xxxxxxxxxx> wrote:
spamtrap@xxxxxxxxxx wrote:
I cannot see the result of ES...
I know "command debug" can reach the goal.
how can use the "command debug"?
"start->run->command" to get a command prompt. Then "debug myprog.com"
(or "myprog.exe"... but debug does better with .com). Then typing '?'
will give a list of commands. The "most important" one is probably 'q' -
quit - so you can get *out* of the damn thing! :) You'll probably want
to "trace" through your program with 't'. When you get to an "int 21h",
use 'p' to "proceed" past it (or you'll be tracing through the "bowels
of dos", which is less helpful than it sounds). 'r' will display (and
optionally set) registers. A google for "debug tutorial" will turn up
more information.
Hope I understood the question.
Best,
Frank
P.S. A "better" debugger here...
http://members.tripod.com/~ladsoft/grdb.htm
Note that DOS Debug doesn't unassemble any
opcode later than those in the original 8088 set.
That means you won't get any 32-bit instructions,
of course, but it also means that you won't get
things like 'SHL AX,2' and a host of others.
This makes it virtually worthless for anything but
really old code, or code you write specifically
with these limitations in mind.
Best regards,
Bob Masta
dqatechATdaqartaDOTcom
D A Q A R T A
Data AcQuisition And Real-Time Analysis
www.daqarta.com
Home of DaqGen, the FREEWARE signal generator
.
- References:
- how can I see the result of the program?
- From: spamtrap
- Re: how can I see the result of the program?
- From: Frank Kotler
- how can I see the result of the program?
- Prev by Date: Re: I have a problem with my study
- Next by Date: Re: OllyDbg used to debug VC2005 applications?
- Previous by thread: Re: how can I see the result of the program?
- Next by thread: I have a problem with my study
- Index(es):
Relevant Pages
|
