[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: assembly debugging

Subject: Re: assembly debugging
From: "BLuRry" <brendan.robert@gmail.com>
Date: 16 Jun 2006 06:21:22 -0700
Complaints-to: groups-abuse@google.com
In-reply-to: <1150461368.455119.144350@c74g2000cwc.googlegroups.com>
Injection-info: r2g2000cwb.googlegroups.com; posting-host=206.210.17.33; posting-account=N5hIbA0AAACzTGVDiZh9ucUYdzqr6aq7
Newsgroups: comp.sys.apple2
Organization: http://groups.google.com
References: <44926c0a$0$932$ba4acef3@news.orange.fr> <1150461368.455119.144350@c74g2000cwc.googlegroups.com>
User-agent: G2/0.2
Xref: g2news2.google.com comp.sys.apple2:9354

schmidtd wrote:
> Guillaume Tello wrote:
> > how to debug a program? to trace it step by step?
> > is the monitor the only solution?
>
> I like to debug with an emulator.  AppleWin
> (http://applewin.berlios.de/) has nice step and inspect capabilities.

I second that.  Using AppleWin's debugger is the best way to inspect
and analyze your code.  You can also import your symbol table so it is
easier to figure out where it is in respect to your code.

(I'd recommend using a cross assembler on something with more than
80x24 characters on the screen -- such as Acme -- but that's just a
personal preference.)

References:
- assembly debugging
  - From: "Guillaume Tello" <houten.van@wanadoo.fr>
- Re: assembly debugging
  - From: "schmidtd" <schmidtd@my-deja.com>

Prev by Date: Re: assembly debugging
Next by Date: Re: assembly debugging
Previous by thread: Re: assembly debugging
Next by thread: Re: assembly debugging
Index(es):
- Date
- Thread