-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging the int-clock device is incompatible with the -t debug flag #1107
Comments
This is indeed a problem. I'm guessing that you only ran into it due to trying to research the problem you described in #1108 which is now fixed. Otherwise it isn't affecting you, right? |
That's correct. I don't think this is a very serious issue at all, I just wanted to make sure it was known about in case it's an easy fix. |
The change that introduced sim_rtcn_get_time was only partially implemented. It was inspired by reports that folks trying to record precise simulator session logs for consistency validation were complaining that behavior was not 100% consistent from one run to the next. These differences were due to timing issues that happened differently depending on variations in host system loading. I was thinking about implementing an "uncalibrated" mode for cases like this so that clock ticks would always take precisely the same number of instruction execution and polling for input would always happen at precisely identical instruction counts. This mode would: not keep simulated wall clock time aligned with real wall clock time and would not work consistently if any network activity was part of things and would not work consistently if manual user input (via TMXR sessions) was part of what was going on. Those constraints are probably OK for automated validation script execution. Since things are working now, I'd like to get this uncalibrated mode implemented completely along with fixing the problem you've reported here. |
Context
Attempting to debug the int-clock device if the -t debug flag is used causes a stack overflow and a crash in all SIMH simulators.
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 was built from current simh master branch at HEAD.
the simulator configuration file (or commands) which were used when the problem occurred.
Reproduction is simple. In any simulator (not just vax):
The problem appears to be a recursive call to
sim_rtcn_get_time
insidesim_debug_prefix()
.The text was updated successfully, but these errors were encountered: