| Newsgroups |
gmane.comp.emulators.hercules390.general |
| Message-ID |
<[email protected]> |
---In [email protected], <dave.g4ugm@...> wrote :
> Whilst I am with you 100% with diagnosis, I can
> see that debugging and fixing this is likely to take
> a lot of work for negligible gain....
It would probably take a lot of work, but I
think eliminating race conditions from
Hercules would be a good idea for a
mature product. Also the problem may
manifest itself elsewhere in the future.
At least the problem is reproducible on
one system.
> Whilst I would assume it already stops the CPUs
> does adding a "STOPALL" before the quit help?
No, stopall doesn't change the result:
06:27:01 HHC01413I Hercules version 4.1.0.9426-SDL-g42b533fa (4.1.0.9426)
...
06:28:40 HHC02264I Script 5: file scripts/tk4-.rc processing ended
06:28:43 HHC01603I stopall
06:28:52 HHC01603I quit
06:28:52 HHC01420I Begin Hercules shutdown
06:28:54 HHC01423I Calling termination routines
06:28:54 HHC00101I Thread id 0000583c, prio 4, name 'socket_thread' ended
06:28:54 HHC00101I Thread id 000054a8, prio 4, name 'http_server' ended
06:28:54 HHC00101I Thread id 00003cb8, prio 2, name 'Processor CP00' ended
06:28:54 HHC00101I Thread id 00004e7c, prio 4, name 'console_connect' ended
06:28:54 HHC00101I Thread id 0000451c, prio 4, name '0:0670 communication thread' ended
06:28:54 HHC00101I Thread id 000047ac, prio 4, name '0:0671 communication thread' ended
06:28:54 HHC00101I Thread id 00003d84, prio 4, name '0:0672 communication thread' ended
06:28:54 HHC00101I Thread id 00001160, prio 4, name '0:0673 communication thread' ended
(log file ends here)
I just noticed that there is a 2-second delay
after the quit. Possibly Hercules has some
"failsafe" 2 second cancel.
BFN. Paul.