-
Notifications
You must be signed in to change notification settings - Fork 94
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
Crashes with "ctc debug" commands #536
Comments
Hi Matthew! I was able to reproduce the crash and am working on a fix right now. Thank you for reporting this. While I have not completed my analysis yet, I believe the bug is being caused by the fact that the device in question has not established a connection to the other system yet, and thus has not fully initialized yet. (Some internal device fields are still NULL.) I suspect if you try the same thing after the device has finished initializing (i.e. has finished connecting to the other system) the crash would probably not occur. But I will try to confirm that. In any case, the problem is being actively looked into and a fix for it will be forthcoming. |
Closes #536. Note: also added support for "ctc debug" command by itself (i.e. without any other operands) to LIST the current CTC debugging state for all CTC devices.
Fixed by commit 0afad3b. Closing. NOTE: As it turns out, the crash was not caused by the CTCE device not being connected. It would have also crashed even if it was already connected. The bug was actually caused by some missing code for CTCE devices in the |
P.S. To get the fix you will of course need to do a |
P.S. #2: I also added support for entering the |
Thanks Fish! I've pulled the develop branch and |
Hercules version: 4.5.0.10830-SDL-g58578601
Host OS: Arch Linux x86_64. Linux kernel version 6.1.1-arch1-1
When I use Hercules console commands such as
ctc debug on 502
andctc debug off 502
, things work as expected. However, if I enter partial commands such asctc debug
orctc debug off
, Hercules crashes with:This also happens with what I believe to be a complete valid command,
ctc debug on all
.This is reproducible with the following minimal hercules.cnf file:
Expected behavior: if the command supplied is incomplete or requires more arguments, I would expect an error message, not a crash. Furthermore, the
help ctc
text suggests to me thatctc debug on
andctc debug off
(without optional device number orALL
keyword) should be valid.The text was updated successfully, but these errors were encountered: