[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: assembly debugging
- Subject: Re: assembly debugging
- From: "mdj" <mdj.mdj@gmail.com>
- Date: 16 Jun 2006 19:54:55 -0700
- Complaints-to: groups-abuse@google.com
- In-reply-to: <4492f257$0$65503$742ec2ed@news.sonic.net>
- Injection-info: r2g2000cwb.googlegroups.com; posting-host=210.49.254.106; posting-account=W_jMEA0AAAAZdNaersJnc-7Hjv-SIC8Q
- Newsgroups: comp.sys.apple2
- Organization: http://groups.google.com
- References: <44926c0a$0$932$ba4acef3@news.orange.fr> <1150465512.321428.151260@c74g2000cwc.googlegroups.com> <4492f257$0$65503$742ec2ed@news.sonic.net>
- User-agent: G2/0.2
- Xref: g2news2.google.com comp.sys.apple2:9372
Andy McFadden wrote:
> Mark Percival <mark@syndicomm.com> wrote:
> >> how to debug a program? to trace it step by step?
> >> is the monitor the only solution?
> >
> > For development of DiskMaker8, I used a hard copy listing and the Apple
> > IIgs's "Visit Monitor" CDA. I also wrote a short routine that would
> > display register contents at any given point. That was a big help too.
>
> If you have a IIgs, GSBug is very handy.
>
> I used GSBug and a ProDev debugger board when working on HardPressed.
ORCA/M also has a debugger, but for some reason it only works with
unenhanced machines...
Matt