When I start a statement with binary data the column INFO of information_schema.processlist is truncated at the first byte > 128. show full processlist shows the full query in it's Info column.
My test query is generated and run by this perl script:
While the sleep is still asleep, use
or look at the info column specifically:
which results in
you can verify that the values are truncated inside the server, this is not a problem with the client connection or the client.
For comparison use
with the result
The character set settings are: