When metadata parsing fails due to badly formatted XML, there is an uncaught
exception that
crashes haggle.
This behavior can be repeated by inserting the following data object into
haggle:
<Haggle>
<Attr name=crash>me</Attr>
</Haggle>
Note that the attribute name and value in and of themselves are ok, but the XML
formatting is
bad.
I get the follwoing output:
Entity: line 2: parser error : AttValue: " or ' expected
<Attr name=crash>me</Attr>
^
Entity: line 2: parser error : attributes construct error
<Attr name=crash>me</Attr>
^
Entity: line 2: parser error : Couldn't find end of Start Tag Attr line 2
<Attr name=crash>me</Attr>
^
Entity: line 2: parser error : Opening and ending tag mismatch: Haggle line 1
and Attr
<Attr name=crash>me</Attr>
^
Entity: line 3: parser error : Extra content at the end of the document
</Haggle>
^
initDoc failed
91.434:void haggle::unexpected_exception_handler(): Uncaught exception in
thread
ProtocolTCPClient:3[Thread:8]!
91.434:void haggle::unexpected_exception_handler(): Please do exception
handling...
Bus error
Please use labels and text to provide additional information.
Original issue reported on code.google.com by daniel.a...@it.uu.se on 31 Aug 2009 at 6:47
Original issue reported on code.google.com by
daniel.a...@it.uu.se
on 31 Aug 2009 at 6:47