[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 6502 Simulator
- Subject: Re: 6502 Simulator
- From: Sheldon Simms <sheldonsimms@yahoo.com>
- Date: Tue, 17 Feb 2004 09:55:51 -0500
- Newsgroups: comp.sys.apple2
- Organization: Posted via Supernews, http://www.supernews.com
- References: <KSgYb.24757$_a5.1279@newssvr27.news.prodigy.com>
- User-agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.)
- Xref: archiver1.google.com comp.sys.apple2:3511
On Tue, 17 Feb 2004 04:35:55 +0000, Shawn B. wrote:
> Now for the reason I'm making it in the first place: when you are debugging,
> and a breakpiont is set, you can modify the source code and next time you
> step the breakpoint, it will execute your new instructions as if you
> originally compiled it that way.
>
> The way I intend to implement this trick is like this: when you chance the
> source, and step the breakpoint, it will then recompile the program (only
> your source code) and overlay the old memory with the new memory and then
> adjust any branches and references as necessary and then adjust the Program
> Counter to the necessary memory location to cause the change to "appear" to
> have taken effect. This way, if I have a nasty defect that I"m trying to
> correct, then I can just keep it in the breakpoint and change the source as
> I'm debugging without having to constantly start over again.
Sounds like a lot of work to me. Why not just allow the user to select
an address in memory (preferably by clicking on it) and then just type in
new instructions which are immediately assembled and and inserted there?