Re: security issue in xerces 2.5.0 and earlier (CAN-2004-1575)

Gareth Reakes <[EMAIL PROTECTED]> wrote: > It would be in the scanners. They are in the internal directory and > end in Scanner (EG DGXMLScanner). For DGXMLScanner the revision number > the code was committed in was 1.54 with message > > "Optimized duplicated attributes checking for large number o

[jira] Closed: (XERCESC-1376) TraverseSchema allocates from the wrong memory manager...

[ http://issues.apache.org/jira/browse/XERCESC-1376?page=history ] Gareth Reakes closed XERCESC-1376: -- All done > TraverseSchema allocates from the wrong memory manager... > - > > Key: X

Re: security issue in xerces 2.5.0 and earlier (CAN-2004-1575)

Hi, Jay Berkenbilt wrote: I posted a question on February 24 about this but got no response, so I would greatly appreciate some advice on the proper way to get help on this issue. Please note that this isn't a complaint -- just a question to make sure I'm going about this the right way. :-) Sorry,

[jira] Commented: (XERCESC-1376) TraverseSchema allocates from the wrong memory manager...

[ http://issues.apache.org/jira/browse/XERCESC-1376?page=comments#action_60768 ] Christian Will commented on XERCESC-1376: - Hi Gareth, I saw your check-in. It looks fine. Thanks, Christian > TraverseSchema allocates from the wrong memory mana

[jira] Commented: (XERCESC-1376) TraverseSchema allocates from the wrong memory manager...

[ http://issues.apache.org/jira/browse/XERCESC-1376?page=comments#action_60762 ] Gareth Reakes commented on XERCESC-1376: Hi Christian, I can't seem to get the patch file from this bug for some reason. Could you mail it to me? [EMAIL PROTECTED]

[jira] Resolved: (XERCESC-1376) TraverseSchema allocates from the wrong memory manager...

[ http://issues.apache.org/jira/browse/XERCESC-1376?page=history ] Gareth Reakes resolved XERCESC-1376: Resolution: Fixed Alby got the attachment for me. Patch in cvs. Could you please verify. > TraverseSchema allocates from the wrong memory ma

[jira] Assigned: (XERCESC-1376) TraverseSchema allocates from the wrong memory manager...

[ http://issues.apache.org/jira/browse/XERCESC-1376?page=history ] Gareth Reakes reassigned XERCESC-1376: -- Assign To: Gareth Reakes > TraverseSchema allocates from the wrong memory manager... > ---

[jira] Resolved: (XERCESC-1375) configure cannot be run due to improper shabang under SunOS

[ http://issues.apache.org/jira/browse/XERCESC-1375?page=history ] Gareth Reakes resolved XERCESC-1375: Resolution: Fixed Fix in cvs. Could you please verify. > configure cannot be run due to improper shabang under SunOS > -

security issue in xerces 2.5.0 and earlier (CAN-2004-1575)

I posted a question on February 24 about this but got no response, so I would greatly appreciate some advice on the proper way to get help on this issue. Please note that this isn't a complaint -- just a question to make sure I'm going about this the right way. :-) I'm asking this question as th

Re: is chars argument in characters( ) call null terminated?

> I'm wondering if I can count on the fact that the > chars argument to the characters( ) method will be a > null terminated array? No, you cannot. > The documentation seems not to indicate either way, > but the fact that the length is passed explicitly > suggests that it is not neccasarily null

[jira] Created: (XERCESC-1377) Error in SAXParser! invalid namespaces

Error in SAXParser! invalid namespaces -- Key: XERCESC-1377 URL: http://issues.apache.org/jira/browse/XERCESC-1377 Project: Xerces-C++ Type: Bug Components: SAX/SAX2 Versions: 2.6.0 Environment: Windows XP Borland Buil

[jira] Updated: (XERCESC-1360) compile error for 64bit solaris binary by GCC 3.3.2

[ http://issues.apache.org/jira/browse/XERCESC-1360?page=history ] Alberto Massari updated XERCESC-1360: - Description: I am trying to build 64 bits xercesc 2.6 with gcc 3.3.2 on SunOS 5.9, and got an error in an assemble file, here my steps: xerces