Groups | Search | Server Info | Login | Register
Groups > comp.emulators.apple2 > #2251
| Newsgroups | comp.emulators.apple2 |
|---|---|
| Date | 2017-02-21 10:10 -0800 |
| References | (2 earlier) <bc36ba00-c65f-46ce-b961-e5fb8c8b04cd@googlegroups.com> <73b17e3e-c1cc-4512-9885-b8c5cef9fc62@googlegroups.com> <907fb263-d80c-4483-80cc-2b59cec96a05@googlegroups.com> <3f769e02-cb4e-41c6-a8d3-0a484e3d6f1f@googlegroups.com> <be1c40e1-01fb-43dd-a7db-b7a3def2c83d@googlegroups.com> |
| Message-ID | <1e08ccc2-3688-4185-a312-bf42a58a6e3e@googlegroups.com> (permalink) |
| Subject | Re: Clues tracking down an emulator bug (San inc crack of Airheart) |
| From | Zellyn <zellyn@gmail.com> |
On Tuesday, February 21, 2017 at 1:00:41 PM UTC-5, BLuRry wrote: > I added JUnit stubs in Jace for this kind of thing. Curious to see what you've come up with. You can write unit tests in Jace which have actual assembler in them and it will use ACME to build the code and then run it. On the java side after plugging the code into memory it will run for the specified number of machine cycles and then assert if the result is correct. For my own emulator, I did this kind of thing: For instance, here you can see a set of instructions that is assembled, then run in parallel on both my emulated 6502 and the "virtual 6502" gate-level simulation: https://github.com/zellyn/go6502/blob/master/tests/compare_test.go#L93 I've now moved on to working to improve OpenEmulator, rather than playing with my own emulator, and I know less about testing it. I also wanted to create a generic emulator test that will help improve every emulator out there. So currently, it's a .DSK image, built with qkumba's "Standard Delivery" loader, so that (a) it'll be fast, and (b) the disk will be mostly trailing zeros so I can transfer it quickly with ADTPro :-) Zellyn
Back to comp.emulators.apple2 | Previous | Next — Previous in thread | Next in thread | Find similar
Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-19 14:51 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-19 17:15 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-19 21:16 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Peter Ferrie <peter.ferrie@gmail.com> - 2017-02-20 10:19 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-20 13:59 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-20 14:42 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Michael AppleWin Debugger Dev <michael.pohoreski@gmail.com> - 2017-02-21 07:56 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-21 08:11 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-21 10:00 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-21 10:10 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) sicklittlemonkey <nick.westgate@gmail.com> - 2017-02-21 19:11 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) gids.rs@sasktel.net - 2017-02-22 09:28 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-22 09:33 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) sicklittlemonkey <nick.westgate@gmail.com> - 2017-02-23 01:46 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-23 06:19 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) gids.rs@sasktel.net - 2017-02-23 08:44 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Michael AppleWin Debugger Dev <michael.pohoreski@gmail.com> - 2017-02-23 21:03 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Steve Nickolas <usotsuki@buric.co> - 2017-02-24 07:14 -0500
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-24 06:07 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) John Brooks <jbrooks@blueshiftinc.com> - 2017-02-24 07:56 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Zellyn <zellyn@gmail.com> - 2017-02-24 09:55 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-24 12:45 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) gids.rs@sasktel.net - 2017-02-24 14:56 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-24 18:37 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Richard Thiebaud <thiebauddick2@aol.com> - 2017-02-24 22:01 -0500
Re: Clues tracking down an emulator bug (San inc crack of Airheart) BLuRry <brendan.robert@gmail.com> - 2017-02-24 21:09 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Richard Thiebaud <thiebauddick2@aol.com> - 2017-02-25 19:42 -0500
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Richard Thiebaud <thiebauddick2@aol.com> - 2017-02-25 19:48 -0500
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Peter Ferrie <peter.ferrie@gmail.com> - 2017-02-21 08:24 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) John Brooks <jbrooks@blueshiftinc.com> - 2017-02-23 18:29 -0800
Re: Clues tracking down an emulator bug (San inc crack of Airheart) Peter Ferrie <peter.ferrie@gmail.com> - 2017-02-21 22:57 -0800
csiph-web