Description:
------------
When you have code that receives data that may be perceived as broken UTF-8 and 
you have a full UTF-8 config for MySQL then MySQL will truncate the backtrace up 
to the first broken byte. 

Suggested fix:

Since APM can not know what data it is dealing with, it should not make any 
assumptions either. Convert the BACKTRACE field in the MySQL schema to the BINARY 
character set:

ALTER TABLE event MODIFY backtrace CHARACTER SET BINARY;


Test script:
---------------
<?php

function h($str)
{
	return htmlspecialchars($str, ENT_QUOTES, 'UTF-8');
}


function stuff($bericht)
{
	$y = h($bericht);
}

stuff("lalala \xE9 bork bork");

Expected result:
----------------
This backtrace:

#0 htmlspecialchars("lalala ? bork bork", 3, "UTF-8") called at [test.php:5]
#1 h("lalala ? bork bork") called at [test.php:11]
#2 stuff("lalala ? bork bork") called at [test.php:14]

Actual result:
--------------
This backtrace:

#0 htmlspecialchars("lalala