libxmlplusplus-general

[libxml++] Unknown encoding crashes DOM Parser

[<p....@ic...>]

The following encoding
      <?xml version="1.0" encoding="ISO-8859-15"?>
leads to a crash under Windows and Linux.

In domparser.cc / DomParser::parse_context() one finds:

xmlParseDocument(_context);
_doc = new Document(_context->myDoc); // context->myDoc is 0 if encoding is
illegal, therefore the constructor segfaults

It should be checked if _context->myDoc is a valid pointer.

Best regards, Peter.

[libxml++] indent again

[<joe...@un...>]

Hi,

I read many things about keeping blanks, whitespaces, indenting etc. (It's=
=20
hard to follow the discussion within the web-interface)

I have only one simple question:

How am I able to produce _readable_ output (I don't really care for indents=
,=20
but some CR would be nice)?

Maybe I didn't get the point, but I got 2 things, that makes me gonna feel=
=20
this is important.
I'm working with big files (some about 8MB), they are really _not_ readable=
 in=20
any kind when there is no <CR>. Secondly the parser is _significantly_=20
slower, when the file is an 8MB xml stream. I don't know why, but version=20
0.21.0 is much faster (with xml produced by this version).

regards - J=F6rn

Re: [libxml++] Unknown encoding crashes DOM Parser

[Christophe de V. <cde...@al...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Le Mardi 10 Juin 2003 13:07, p....@ic... a =E9crit :
> The following encoding
>       <?xml version=3D"1.0" encoding=3D"ISO-8859-15"?>
> leads to a crash under Windows and Linux.
>
> In domparser.cc / DomParser::parse_context() one finds:
>
> xmlParseDocument(_context);
> _doc =3D new Document(_context->myDoc); // context->myDoc is 0 if encodin=
g is
> illegal, therefore the constructor segfaults
>
> It should be checked if _context->myDoc is a valid pointer.
>

Thanks for pointing this problem.

I wonder if it would be enough to move the _doc initialisation lower, after=
=20
_context->wellFormed and _context->valid are checked ?
In other terms, does _context->wellFormed and _context->valid implies=20
_context->myDoc ?
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+5vT0B+sU3TyOQjARAmktAJ4skoiSOiVChiw331oTWe+KsYc+iwCgtxmj
aEaOjyi9PFyk7jkp6JnXN84=3D
=3D2Imr
=2D----END PGP SIGNATURE-----

Re: [libxml++] Unknown encoding crashes DOM Parser

[Christophe de V. <cde...@al...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le Mercredi 11 Juin 2003 11:23, Christophe de VIENNE a =E9crit :
> I wonder if it would be enough to move the _doc initialisation lower, aft=
er
> _context->wellFormed and _context->valid are checked ?
> In other terms, does _context->wellFormed and _context->valid implies
> _context->myDoc ?
>
>

It seems that no. I'll investigate this a bit more.
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+5vhnB+sU3TyOQjARAvFJAKDTTHmgSqu55BYZlOxgBKJcPy+4IwCfXSBF
fKH9FK8qTAsiWYSRwY6fI4E=3D
=3DkwnL
=2D----END PGP SIGNATURE-----

Re: [libxml++] Unknown encoding crashes DOM Parser

[<p....@ic...>]

> I wonder if it would be enough to move the _doc initialisation lower,
after
> _context->wellFormed and _context->valid are checked ?
> In other terms, does _context->wellFormed and _context->valid implies
> _context->myDoc ?

I tested this assumption and the answer is no. The program still segfaults
when moving the _doc initialization downward.

Best regards, Peter.