Closed cyourth-cognonic closed 4 years ago
Hi Clinton,
The issue template you were filling out asked to provide: "sim> SHOW VERSION" while running the simulator which is having the issue"
I was trying to suggest that ALL of the output that was produced, not merely suggesting that you pick a little of it. Please suggest language that I can use in the template that would have inspired you to provide all of it, and I'll update the template.
As soon as you provide the requested output, I'll engage the author to fix the problem you found.
Thanks.
updated show version details...
You're running a version from last November. Please pick up the latest source from https://github.com/simh/simh and confirm that this has not yet been fixed.
Thanks.
I'm using the 4.0.x release, not 3.11.x - this has not been fixed for any release....
Since anyone can grab the latest code at any time, the current code base does not have a formal release process. The swtp6800 simulators are no longer part of Bob Supnik's 3.11 release but they're maintained here. The issue reporting system specifically asks for the full output of SHOW VERSION so that we can precisely determine what you may be working with.
I don't know how/where you got what you're working with now, but the latest can always be picked up with either from:
$ git clone https://github.com/simh/simh
$ cd simh
$ make {simulator-name(s)}
$# simulators are in the BIN subdirectory
OR
download:
$ wget https://github.com/simh/simh/archive/master.zip
$ wget https://github.com/simh/simh/archive/master.tar.gz
Then build with:
$ unzip master.zip
$ cd simh_master
$ make {simulator-name(s)}
For the above to work and the build to complete, you'll need: git (maybe), wget(maybe), unzip, gcc (or clang), and make.
Testing latest version - still same issue - incorrect address for SWI vector...
Context
Running SWTP 6800 simulation and testing the SWTBug Monitor with SWI based code. The simulation is exiting back to SIMH command line with the following error:
the output of "sim> SHOW VERSION" while running the simulator which is having the issue
how you built the simulator or that you're using prebuilt binaries
the simulator configuration file (or commands) which were used when the problem occurred.
the expected behavior and the actual behavior
changes to make it work