From: Daniel Veillard (Daniel.Veillard@w3.org)
Date: Fri Sep 22 2000 - 17:35:51 EDT
> > In your case, the problem comes from doc being NULL when calling the
> > entity resolution routine. This bug was fixed in the last month, so what
> > version are you using ???
>
> 2.2.2, so that might explain it. I apologize, I might have missed the
> discussion about this. I'll upgrade and give it another shot.
I don't think it was dicussed in the ML. But I'm pretty sure I
fixed this.
The problem was the following:
- you were adding an argument to a node
- this node had not (yet ?) been connected to a document
- when adding an attribute, the string has to be parsed to
possibly split it into text nodes and entity references node
- there was an entity reference, but the document pointer was
NULL.
- the fix is that the entity lookup should not have crashed due
to this, it should just lookup the predefined entity references.
- however if that attribute value had referenced a locally defined
entity then since the node has not been connected, it's not possible
to find the document and hence the list of declared entities.
So it's better anyway to connect first the node to the document before
adding attributes or content to it.
If the node was connected to the document then it's another bug and
try to give me the sequence of call you made since the creation of the
element.
Daniel
-- Daniel.Veillard@w3.org | W3C, INRIA Rhone-Alpes | Today's Bookmarks : Tel : +33 476 615 257 | 655, avenue de l'Europe | Linux XML libxml WWW Fax : +33 476 615 207 | 38330 Montbonnot FRANCE | Gnome rpm2html rpmfind http://www.w3.org/People/all#veillard%40w3.org | RPM badminton Kaffe ---- Message from the list xml@rpmfind.net Archived at : http://xmlsoft.org/messages/ to unsubscribe: echo "unsubscribe xml" | mail majordomo@rpmfind.net
This archive was generated by hypermail 2b29 : Fri Sep 22 2000 - 17:43:26 EDT