RE: Encoding mismatch can crash sax parser

[Peter Fein]

1.4.  I downloaded it on 1/30.  I will test with the latest build. 

 

Thanks.

-----Original Message-----
From: Khaled Noaman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 2001 5:13 PM
To: [EMAIL PROTECTED]
Subject: Re: Encoding mismatch can crash sax parser

Peter,

What release of XML4C are you using?
That problem was reported and fixed a while back.
Would you please download the latest nightly build and try again.

Khaled

Dean Roddey wrote:

Someone already reported that one, but not sure if its been fixed yet.

--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]

-----Original Message-----
From: Peter Fein [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 2001 11:30 AM
To: [EMAIL PROTECTED]
Subject: Encoding mismatch can crash sax parser

A UTF-8 document that has the encoding declaration set to utf-16 can crash
the sax parser.  The autosense code works correctly but there is a bug in
XMLReader::setEncoding.  fEncodingStr is prematurely deleted and nulled out
before the code realizes that it contains the correct value.  Later in
XMLTransService::makeNewTranscoderFor, the zeroed fEncodingStr is
dereferenced causing an access violation.

The following document demonstrates the problem:

<?xml version="1.0" encoding="utf-16"?>
<document/>

I believe the fix is to wait until after we pass the "return false" cases in
XMLReader::setEncoding to delete fEncodingStr.  I am testing it now.

Peter Fein
[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]