Groups | Search | Server Info | Login | Register


Groups > comp.sys.apple2.programmer > #6338

Re: Integrated development on emulators: The next step

Path csiph.com!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From D Finnigan <dog_cow@macgui.com>
Newsgroups comp.sys.apple2.programmer, comp.emulators.apple2
Subject Re: Integrated development on emulators: The next step
Date Tue, 14 Oct 2025 19:18:02 -0000 (UTC)
Organization Mac GUI
Lines 20
Message-ID <dog_cow-1760469480@macgui.com> (permalink)
References <dog_cow-1759848430@macgui.com> <alpine.DEB.2.21.2510080804400.25129@sd-119843.dedibox.fr> <10c6ejt$1qvka$1@dont-email.me>
MIME-Version 1.0
Content-Type text/plain; charset=UTF-8
Content-Transfer-Encoding 8bit
Injection-Date Tue, 14 Oct 2025 19:18:04 +0000 (UTC)
Injection-Info dont-email.me; posting-host="afcd13583c0682a10d6bba7dd27eb390"; logging-data="3336442"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/UqEQNOS1RxH1pSfCs0hN5"
User-Agent Mac GUI Usenet
Cancel-Lock sha1:OPsco/1VOGHQ2vTYd7NR1DEgGPM=
In-Reply-To <10c6ejt$1qvka$1@dont-email.me>
Xref csiph.com comp.sys.apple2.programmer:6338 comp.emulators.apple2:3911

Cross-posted to 2 groups.

Show key headers only | View raw


Kent Dickey wrote:
> 
> Most emulators allow easy loading of external files into memory, and
> this can be scripted.  So you build on your host machine, then load
> the binary into the emulator.
> 

That's true, and that would be a good starting point for some extensions to
aid development. But imagine a closely-coupled assembler where you could set
a breakpoint in the source file, and then start the emulated machine
running. As soon as execution reaches that breakpoint, there is a marker in
the source, and you can single step through the object code and see all
register values, etc. No more tracing through the Monitor, instead you trace
through your assembly source.

-- 
]DF$
The New Apple II User's Guide:
https://macgui.com/newa2guide/

Back to comp.sys.apple2.programmer | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Integrated development on emulators: The next step D Finnigan <dog_cow@macgui.com> - 2025-10-07 14:47 +0000
  Re: Integrated development on emulators: The next step Steve Nickolas <usotsuki@buric.co> - 2025-10-08 08:09 -0400
    Re: Integrated development on emulators: The next step mummycullen@gmail-dot-com.no-spam.invalid (MummyChunk) - 2025-10-08 13:31 -0400
      Re: Integrated development on emulators: The next step Steve Nickolas <usotsuki@buric.co> - 2025-10-08 20:36 -0400
      Re: Integrated development on emulators: The next step Speccie <someone@somewhere.com> - 2025-10-09 08:07 +0100
        Re: Integrated development on emulators: The next step Hugh Hood <hughhood@earthlink.net> - 2025-10-09 10:44 -0500
          Re: Integrated development on emulators: The next step Speccie <someone@somewhere.com> - 2025-10-10 08:01 +0100
      Re: Integrated development on emulators: The next step D Finnigan <dog_cow@macgui.com> - 2025-10-14 19:14 +0000
    Re: Integrated development on emulators: The next step kegs@provalid.com (Kent Dickey) - 2025-10-08 19:38 +0000
      Re: Integrated development on emulators: The next step D Finnigan <dog_cow@macgui.com> - 2025-10-14 19:18 +0000
      Re: Integrated development on emulators: The next step Hugh Hood <hughhood@earthlink.net> - 2025-10-15 23:28 -0500
        Re: Integrated development on emulators: The next step kegs@provalid.com (Kent Dickey) - 2025-10-20 19:05 +0000
      Re: Integrated development on emulators: The next step Noncho Savov <user10020@newsgrouper.org.invalid> - 2025-10-26 20:49 +0000

csiph-web