[Bug 46045] New: Failed to parse logs with binary (invalid xmlChar)

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=46045

             Bug #: 46045
           Summary: Failed to parse logs with binary (invalid xmlChar)
    Classification: Unclassified
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: logger
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: l.bigonville at edpnet.be
         QAContact: telepathy-bugs at lists.freedesktop.org


Hi,

Yesterday I've been able to inject binary into the log of one of my conversation and this morning I saw that I cannot get the backlog.


The logs show me that:

/home/bigon/.local/share/TpLogger/logs/gabble_jabber_bigon_40foo_2ebe0/my at contact/20120213.log:202: parser error : xmlParseCharRef: invalid xmlChar value 1
 message-token='0395044b-cf55-4bb0-906e-5c0d128ae778'>retourne 10.0.100.18 
                                                                               ^
/home/bigon/.local/share/TpLogger/logs/gabble_jabber_bigon_40foo_2ebe0/my at contact/20120213.log:202: parser error : xmlParseCharRef: invalid xmlChar value 2
age-token='0395044b-cf55-4bb0-906e-5c0d128ae778'>retourne 10.0.100.18 
                                                                               ^
/home/bigon/.local/share/TpLogger/logs/gabble_jabber_bigon_40foo_2ebe0/my at contact/20120213.log:202: parser error : xmlParseCharRef: invalid xmlChar value 2
4b-cf55-4bb0-906e-5c0d128ae778'>retourne 10.0.100.18 __MSBROWSE__
                                                                               ^

(gnome-shell:2170): tp-logger-WARNING **: Failed to parse file:'/home/bigon/.local/share/TpLogger/logs/gabble_jabber_bigon_40foo_2ebe0/my at contact/20120213.log'

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.