This is my suggested fix for #53, which prevents debug messages from displaying during the getVTInfo function. As noted in the issue, the while loop in getVTInfo is prone to silent failure and endless looping (#29) and the lack of debug info even when the --debug switch is applied makes it look like everything is fine if you're not familiar with the program's normal output.
The fix is simply to supply the args.debug value to the getVTInfo function, as appears to be standard elsewhere in the application.
This is my suggested fix for #53, which prevents debug messages from displaying during the
getVTInfofunction. As noted in the issue, the while loop ingetVTInfois prone to silent failure and endless looping (#29) and the lack of debug info even when the--debugswitch is applied makes it look like everything is fine if you're not familiar with the program's normal output.The fix is simply to supply the
args.debugvalue to thegetVTInfofunction, as appears to be standard elsewhere in the application.