[Coco] Re: CoCo related question? (Better edit for coco3.rom)
John R. Hogerhuis
jhoger at pobox.com
Tue Mar 29 16:47:06 EST 2005
On Tue, 2005-03-29 at 16:29 -0500, Albert Stinger wrote:
> I have been using the JV emulator, I patched the bytes
> into the coco3.rom and start the emulator then I run
> edit to see what it does. Let me ask if the program
> crashes can I go into the debugger and be at the
> place I crashed at?
Well, the call stack is shown in the debugger, so maybe. But that isn't
how I would do it.
You need to set a breakpoint on your edit code, try your EDIT, assuming
it is even getting to the edit code, then single step tlll you find the
fault. If it isn't getting to your edit code at all, you need to put
your breakpoint on the BASIC dispatcher (interpreter).
> "John R. Hogerhuis" <jhoger at pobox.com> wrote
> in message news:1112121752.3744.362.camel at aragorn...
> > On Mon, 2005-03-28 at 22:00 -0500, Albert Stinger wrote:
> >> You see my idea is to have EDITEX run entirely from ROM
> >> and not depend on what's in the RAM when patched by
> >> Super Extended Basic. Like I said I want it to be able
> >> to do a regular EDIT commands on the current line number
> >> and have cursor key movement and insert/overstrike at
> >> current cursor location, but looks like it's not so simple.
> >> It starting to look like a lot of work. I need to understand
> >> how BASIC is working better before I'll succeed. I could
> >> use someone with more knowledge to guide me some.
> > How are you testing? The Jeff Vavasour emulator has a nice debugger
> > built into it. Then you could step through your patch and see exactly
> > where it is blowing up.
> > -- John.
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
More information about the Coco