Comment 7 for bug 271252

I believe the root cause of this problem is that the lex grammar in libapparmor used for parsing log messages is not robust enough.

I spent a bit of time instrumenting logprof and found that the garbage characters are printed in the middle of when it calls LibAppArmor::parse_record. This function in libapparmor uses yacc and lex to parse log messages, but when the lex scanner encounters characters that don't match the grammar that has been specified, the default is to print those characters. I think that's what's happening here.