pser1 wrote: ↑Wed May 13, 2026 1:59 pm
Just a side note ... I asume that right now I have two installations ...
But there is only one 'xroar' folder
Could I asume that the contents of src/xroar and usr/bin/xroar are the very same?
will call them next time I switch to Ubuntu
I forgot you asked this...
The checkout of the git repo and the build you made within it doesn't tie into the OS package management at all. You basically just have a directory there with another version in it. When you build from source you can "sudo make install" and it'll put a copy in /usr/local/bin (which should be in your PATH), but you don't have to - and I don't believe you have been, so you'll find that just typing "xroar" with on path launches the version in the package.
Hi Ciaran,
right, I have modified the bash files so that they call the xroar installed (v1.11), not the old one (v1.10)
My question is ...
Could I remove the xroar folder? With no negative side effects?
Of course I will save some files I have created and saved into it.
cheers!
pere
Absolutely, it's just a checkout of the git repo - you can always check it out again if you end up needing to test some other work-in-progress code. General bugfixes I tend to push to the repos and you'll get them when you apt update / apt upgrade.
Hi Ciaran,
I am debugging with GBD the OS9-L2 boot procedure on a Dragon64 emulation (module iMMUnity)
To avoid repeating long sequences, I have saved two snapshots of XRoar at two points I would like to test more times ...
The files have been created as .SNAP without issues.
But, when I restart GDB-Xroar, I do set a breakpoint at the code line after the point I saved the snapshot and I have also
created a pair of watchpoints to detect access to memory at $0050 and $0051
Once done, I issue cont on GDB and then I do load the snapshot on XRoar, but it gets never stopped by GDB
Even setting the breakpoint for the second snapshot and then loading the very first one on XRoar doesn't work for me
I am sure I am doing something wrongly but cannot tell what it is
Any hint would be highly appreciated
thanks beforehand
pere
I'll need to do some testing, but I have a suspicion that loading a snapshot may reset something that shouldn't be reset... If so I'll try and get a fix out
Might be tricky: loading a snapshot tears down the entire machine and then creates a new one, CPU included, and the breakpoints may all be associated with the old machine...
sixxie wrote: ↑Fri Jul 03, 2026 8:09 am
I'll need to do some testing, but I have a suspicion that loading a snapshot may reset something that shouldn't be reset... If so I'll try and get a fix out
Might be tricky: loading a snapshot tears down the entire machine and then creates a new one, CPU included, and the breakpoints may all be associated with the old machine...
Hi Ciaran,
I understand, do not waste too much time. I can live setting two-three temporary breakpoints to get to almost any point by now
It was just a question to know if I was doing something the wrong way!
cheers!
pere
