DO_COMMAND(do_zap)
{
struct session *sesptr;
char arg1[BUFFER_SIZE];
push_call("do_zap(%p,%p)",ses,arg);
sub_arg_in_braces(ses, arg, arg1, GET_ALL, SUB_VAR
DO_COMMAND(do_zap)
{
struct session *sesptr;
char arg1[BUFFER_SIZE];
push_call("do_zap(%p,%p)",ses,arg);
sub_arg_in_braces(ses, arg, arg1, GET_ALL, SUB_VAR
I've combed through the raw client logs of 20 or so instances of this #zap being triggered while driving, and there is nothing obvious to me that is being received that could trigger some niche command or client crash (no strange characters or pseudo-code for example):
But this is still a very reliable, apparently deliberate trigger of a session kill by what is known to be a pretty stable and unflappable piece of software, so I am very puzzled what is going on. I also lack the expertise to file intelligent bug reports with the TT++ devs, so I am curious if anyone smarter than me sees something that might be falsely triggered in the code here.