This repository was archived by the owner on Aug 5, 2022. It is now read-only.
Print the file and line number context in libxml2 error messages #292
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
@krocard Please review. I intend to publish RC3 after this is merged. |
dawagner
force-pushed
the
better-libxml2-error-messages
branch
2 times, most recently
from
b8cfac8 to
1015c96
Compare
This used to be done by libxml2 itself when using the "generic error handler" but was lost when switching to the "structured error handler". Unfortunately, we do not have as much context as with the generic handler, which used to also print the incriminated content and point to the exact location of the error. I didn't find any easy way to get it. Signed-off-by: David Wagner <david.wagner@intel.com>
Contributor
|
|
dawagner
added a commit
that referenced
this pull request
Oct 20, 2015
Print the file and line number context in libxml2 error messages
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This used to be done by libxml2 itself when using the "generic error handler"
but was lost when switching to the "structured error handler".
Unfortunately, we do not have as much context as with the generic handler,
which used to also print the incriminated content and point to the exact
location of the error. I didn't find any easy way to get it.
Signed-off-by: David Wagner david.wagner@intel.com
