Forums Bug Reports Tokenization through /debug seems to break CAP neg

So, I had an issue with mIRC and ZNC, the issue being that mIRC did not request the znc.in/server-time-iso CAP when connecting to ZNC. I finally tracked down the issue as to why it didn't, and it turns out mIRC didn't request the multi-prefix CAP either because of this.

I have a script that is processing /debug output, now here comes the problem: I use /tokenize in that script and it seems to break CAP negotiation. Using $gettok to try to get around the problem and use variables instead also breaks CAP negotiation.

When I disable this script mIRC will happily request these 3 CAPs: userhost-in-names multi-prefix znc.in/server-time-iso when they appear in CAP LS. When I enable this script again mIRC will only request userhost-in-names, eventhough the other CAPs are still listed in LS. Very strange.

Here is a sample script that demonstrates this bug:

Then, execute this command:

And then connect to ZNC.

Here is sample debug output when its breaking:

And here is sample debug output when its working correctly (when commenting out that var line in the debugtest alias):


I'm using mIRC 7.41.

Thanks for your bug report. I was able to reproduce this and tracked it down to the use of strtok(), used for tokenization in a number of routines. It turns out that strtok() uses an internal static variable which prevents it from being used in more than one context in a single-threaded application. I have updated all routines to use strtok_s() which is a security enhanced version of strtok() that resolves this issue. This change will be in the next version.

You're welcome, thank you for fixing it so quick.