Comments

edited

Hi there, I've also been seeing this error for many months now, first while running master prior to the official release of 2.6.1, but after moving to running 2.6.1 release I noticed that I'm still seeing this error, it looks like the NUL maybe isn't handled properly? I'm not totally sure, even though the NUL I don't think is supposed to be there (probably not following the RFC for the IRC protocol)... is throwing this error the proper way to address/handle that?

This comment has been minimized.

Hi, it is possibly indicating some bug or improvement that could be made, but it's hard to tell from just the error messages which code path is responsible for emitting them. It would be best if you could provide a pcap file that reproduces the errors, or, if you can't share that, give a call stack trace that pinpoints file/line information to pinpoint where those errors are generated.