archive.worldofdragon.org

Starting xroar with -trace should print a disassembly of every instruction on console, isn't it?
On windows with xroar-0.30.2-gtk-w32.exe and the normal non-GTK version it does nothing on console. But it runs slower.

EDIT: btw. on http://www.6809.org.uk/dragon/xroar.shtml should be inserted this:

tormod wrote:Those who want to run XRoar on Debian/Ubuntu without building it themselves can use my PPA (personal package archive) at https://launchpad.net/~tormodvolden/+archive/m6809

jedie wrote:Starting xroar with -trace should print a disassembly of every instruction on console, isn't it?
On windows with xroar-0.30.2-gtk-w32.exe and the normal non-GTK version it does nothing on console. But it runs slower.

An artefact of how SDL handles Windows, I'm afraid. Or maybe it's MinGW. Not sure.

Anyway, you'll find the output in a file called "stdout.txt". Not ideal, I know - one of the ways I debug is to pipe standard out through "less" then search for regular expressions on the fly. I suppose you could start up XRoar and then separately run "tail -f stdout.txt | less" (or the DOS equivalent).

Ah! Yes, the stdout.txt is full of content. Great!

EDIT: I would have liked to know that earlier -> viewtopic.php?f=5&t=4308&p=9574#p9574

@sixxie: Under the point http://www.6809.org.uk/dragon/xroar-man ... -shortcuts is Control+V for trace missing

I've found another bug and unlike the last time I'm pretty sure it's a real bug this time . When importing .bas files XRoar truncates lines with 250 or more characters. For a few examples see my latest upload.

Wahey

I'll have a look into it soon.

Edit: ok I had a quick idea to test straight away - I loaded in the .cas version then saved it to another .cas with CSAVE"FOO",A. The saved file includes all the characters, but it does not read back in correctly. As it's reading back a .cas file, XRoar's ASCII munging doesn't come into play, so until I look further, my initial guess is that it's a bug in BASIC.

Further: you can't actually type in line 860 (v3) without deleting the space before and after DATA. BASIC helpfully puts one of those spaces back in when you save as ASCII, so the line will still be corrupted when read back. You can modify the .bas file to exclude both spaces though.

sixxie wrote:my initial guess is that it's a bug in BASIC.

You are correct. I mentioned this bug (and a fix) at the old forum.

sixxie wrote:Further: you can't actually type in line 860 (v3) without deleting the space before and after DATA.

Line 860 (v3) is exactly the same as line 900 from the original (v1) listing, since there is no warning about typing in this line I can only assume that Mr. Cadge arrived at this line after using the line editor.