Description of problem:
I would like to be able to see a context output similar to what a compiler gives on XML parsing errors
Parsing error too many >
Line 435, Column 35:
<element>Funky Text</elemnt>> <thingy/>
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Fixed in upstream:
Author: Peter Krempa <email@example.com>
Date: Tue Sep 6 15:48:22 2011 +0800
XML: Improve XML parsing error messages
This patch modifies error handling function for the XML parser provided
Originaly only a line number and error message were logged. With this
new error handler function, the user is provided with a more complex
description of the parsing error.
Context of the error is printed in libXML2 style and filename of the
file, that caused the error is printed. Example of an parse error:
13:41:36.262: 16032: error : catchXMLError:706 :
/etc/libvirt/qemu/rh_bad.xml:58: Opening and ending tag mismatch: name
line 2 and domain
Context of the error gives the user hints that may help to quickly
locate a corrupt xml file.
Verified this issue with:
1.# virsh edit 2
error: (domain_definition):5: StartTag: invalid element name
2012-01-10 03:07:45.056+0000: 1812: error : catchXMLError:711 : (domain_definition):5: StartTag: invalid element name
So change the status to VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
No Documentation needed
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.