Re: Why doesn't DOMPrint parse this:
Vijay S. Bajwa wrote: David Bertoni apache.org> writes: Vijay S. Bajwa wrote: Trying to get DOMPrint to do schema validation with the following. Why doesn't it look at the schema? Why does it not know that xsi is a namespace defined by by the xmlns attribute? When I turn on the namespace option (-n) it just hangs there! Thanks for help! - Vijay Without enabling namespace processing, you will get DTD validation, so you get validation errors. If, when you enable namespace processing, the parser just "hangs there," perhaps there's something in your schema document that's the culprit. For example, there may be URLs in your schema document that the parser is trying to dereference. Dave The schema doc is below. It is clearly trying to reach these URI's because if I take these out, then it complains "xs" is not associated with any URI. What is the problem with the schema? Really appreciate help as I'm new to this whole thing. (not trying to get out on the cheap, have pored over lots of specs...): Namespace declarations like: xmlns:xs="http://www.w3.org/2001/XMLSchema"; are _never_ dereferenced by the parser. http://citigroup.com/gts/oasys"; xmlns:xs="http://www.w3.org/2001/XMLSche ma" elementFormDefault="unqualified" attributeFormDefault="unqualified"> Bundled eqty block plus all allocs (upto 10,000) maxOccurs="1"/> ... Since you've snipped out the rest of the schema document, it's hard to say what might be going on. For the most part, only xs:include and xs:import elements result in the parser dereferencing URLs. You can find out what's going on by implementing the EntityResolver abstract base class, and installing an instance of your implementation into the parser. You could then set breakpoints in the resolveEntity() function, or write the values of the parameters to stderr, or something like that. If the parser is not stalled trying to load URLs, then there must be some other reason why it is unable to load your schema document. In that case, you'll need to use the debugger to figure out what's going on. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why doesn't DOMPrint parse this:
David Bertoni apache.org> writes: > > Vijay S. Bajwa wrote: > > Trying to get DOMPrint to do schema validation with the following. Why doesn't > > it look at the schema? Why does it not know that xsi is a namespace defined by > > by the xmlns attribute? When I turn on the namespace option (-n) it just hangs > > there! Thanks for help! - Vijay > > Without enabling namespace processing, you will get DTD validation, so you > get validation errors. > > If, when you enable namespace processing, the parser just "hangs there," > perhaps there's something in your schema document that's the culprit. For > example, there may be URLs in your schema document that the parser is > trying to dereference. > > Dave > The schema doc is below. It is clearly trying to reach these URI's because if I take these out, then it complains "xs" is not associated with any URI. What is the problem with the schema? Really appreciate help as I'm new to this whole thing. (not trying to get out on the cheap, have pored over lots of specs...): http://citigroup.com/gts/oasys"; xmlns:xs="http://www.w3.org/2001/XMLSche ma" elementFormDefault="unqualified" attributeFormDefault="unqualified"> Bundled eqty block plus all allocs (upto 10,000) ... Thanks! Vijay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why doesn't DOMPrint parse this:
Vijay S. Bajwa wrote: Trying to get DOMPrint to do schema validation with the following. Why doesn't it look at the schema? Why does it not know that xsi is a namespace defined by by the xmlns attribute? When I turn on the namespace option (-n) it just hangs there! Thanks for help! - Vijay Without enabling namespace processing, you will get DTD validation, so you get validation errors. If, when you enable namespace processing, the parser just "hangs there," perhaps there's something in your schema document that's the culprit. For example, there may be URLs in your schema document that the parser is trying to dereference. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Why doesn't DOMPrint parse this:
Trying to get DOMPrint to do schema validation with the following. Why doesn't it look at the schema? Why does it not know that xsi is a namespace defined by by the xmlns attribute? When I turn on the namespace option (-n) it just hangs there! Thanks for help! - Vijay $ DOMPrint -v=always -s -f gtsEquityBlock.xml Error at file "/home/vb11258/work/zas_apps/cmd/EASL/DOMPrint/gtsEquityBlock.xml", line 3, column 16 Message: Unknown element 'gtsEquityBlock' Error at file "/home/vb11258/work/zas_apps/cmd/EASL/DOMPrint/gtsEquityBlock.xml", line 3, column 27 Message: Attribute 'xmlns:xsi' is not declared for element 'gtsEquityBlock' Error at file "/home/vb11258/work/zas_apps/cmd/EASL/DOMPrint/gtsEquityBlock.xml", line 3, column 101 Message: Attribute 'xsi:noNamespaceSchemaLocation' is not declared for element 'gtsEquityBlock' Error at file "/home/vb11258/work/zas_apps/cmd/EASL/DOMPrint/gtsEquityBlock.xml", line 4, column 9 Message: Unknown element 'msgHdr' . . gtsEquityBlock.xml http://www.w3.org/2001/XMLSchema-instance";> 2147483647 11 4096 ... ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (XERCESC-1642) My application crashed on Solaris Sparc (64bit) using compiler CC(Sun C++ 5.5 Patch 113817-14 2005/07/19 ) and OS 5.8
[
http://issues.apache.org/jira/browse/XERCESC-1642?page=comments#action_12456838
]
Alberto Massari commented on XERCESC-1642:
--
Hi Riaj,
I haven't tried running the code yet, but this function is wrong:
InputSource* MemParseHandlers::resolveEntity(const XMLCh* const publicId, const
XMLCh* const systemId
, const XMLCh* constbaseURL
)
{
XERCES_STD_QUALIFIER cout << "\n MemParseHandlers::resolveEntity called
:\n";
XMLCh* myURL = (XMLCh*)baseURL;
//serving, memory will be deleted by MemBufInputSource because
//the argument adoptBuffer is set to true.
string *ss;
ss = new string(gXSDMemBuf);
// char *tempStr = (char *) malloc ((strlen(gXSDMemBuf) + 1) * sizeof
(char));
// strcpy (tempStr, gXSDMemBuf);
MemBufInputSource* inputSource = new MemBufInputSource ((const
XMLByte*)ss->c_str()
, ss->length()
, ss->c_str()
, true);
return inputSource;
}
You create a MemBufInputSource that adopts the buffer, but you are passing in
the result of ss->c_str() that is not what you allocated; please try with
char *tempStr = new char[strlen(gXSDMemBuf) + 1];
strcpy (tempStr, gXSDMemBuf);
and let us know
Alberto
> My application crashed on Solaris Sparc (64bit) using compiler CC(Sun C++ 5.5
> Patch 113817-14 2005/07/19 ) and OS 5.8
> -
>
> Key: XERCESC-1642
> URL: http://issues.apache.org/jira/browse/XERCESC-1642
> Project: Xerces-C++
> Issue Type: Bug
>Affects Versions: 2.7.0
> Environment: OS : SunOS 5.8 Generic_108528-24 sun4u sparc
> SUNW,Sun-Fire-V440 Solaris
> Compiler : CC: Sun C++ 5.5 Patch 113817-14 2005/07/19
> Xercers: xercesc_2_7
>Reporter: Riaj Mohammed
>Priority: Critical
> Attachments: MemParse.tar
>
>
> I have build the xerces library successfully on solaris 64 bit, but at the
> run time, I get a SIGBUS
>
> The stack trace is
>
> signal BUS (invalid address alignment) in realfree at 0x77d4a2ec
> 0x77d4a2ec: realfree+0x0078:ldx [%i0 + 16], %o1
> Current function is xercesc_2_7::MemoryManagerImpl::deallocate
>47 ::operator delete(p);
>
>
> [1] realfree(0x107eb2524, 0x77ec1780, 0x107eb1990,
> 0x77eb4f60, 0x107eb1980, 0xba7)
> [2] _free_unlocked(0x77ec1668, 0x77eb4f60, 0x1080098b0,
> 0x785069c4, 0x1080
> [3] free(0x1080098b0, 0x0, 0x106c5c460, 0x785069c4,
> 0x7ef013c0, 0x0), at 0xfff
> [4] operator delete(0x1080098b0, 0x106c5c4b0, 0xe, 0x785069c4,
> 0x7f72c930, 0x0), a
> =>[5] xercesc_2_7::MemoryManagerImpl::deallocate(this = 0x106c06b30, p =
> 0x1080098b0), line 47 in "M
> [6] xercesc_2_7::XMLBuffer::~XMLBuffer(this = 0x108009838), line 76 in
> "XMLBuffer.hpp"
> [7] xercesc_2_7::SchemaValidator::~SchemaValidator(this = 0x1080097d8),
> line 340 in "SchemaValidat
> [8] __SLIP.DELETER__L(0x1080097d8, 0x1, 0x7dc000e8,
> 0x785069c4, 0x765f0024, 0x0),
> [9] xercesc_2_7::IGXMLScanner::cleanUp(this = 0x1080043a8), line 559 in
> "IGXMLScanner.cpp"
> [10] xercesc_2_7::IGXMLScanner::~IGXMLScanner(this = 0x1080043a8), line 158
> in "IGXMLScanner.cpp"
> [11] __SLIP.DELETER__P(0x1080043a8, 0x1, 0x7f72c930,
> 0x7ef013c0, 0x7ef013c
> [12] xercesc_2_7::AbstractDOMParser::cleanUp(this = 0x7ffedfb0),
> line 160 in "AbstractDOMP
> [13] xercesc_2_7::AbstractDOMParser::~AbstractDOMParser(this =
> 0x7ffedfb0), line 128 in "A
> [14] xercesc_2_7::XercesDOMParser::~XercesDOMParser(this =
> 0x7ffedfb0), line 65 in "Xerces
> [15] xercesc_2_7::XSDDOMParser::~XSDDOMParser(this = 0x7ffedfb0),
> line 64 in "XSDDOMParser
> [16] xercesc_2_7::IGXMLScanner::resolveSchemaGrammar(this = 0x107fcefb8,
> loc = 0x107fd5fa0, uri =
> [17] xercesc_2_7::IGXMLScanner::scanRawAttrListforNameSpaces(this =
> 0x107fcefb8, attCount = 2), li
> [18] xercesc_2_7::IGXMLScanner::scanStartTagNS(this = 0x107fcefb8, gotData
> = true), line 2211 in "
> [19] xercesc_2_7::IGXMLScanner::scanContent(this = 0x107fcefb8), line 889
> in "IGXMLScanner.cpp"
> [20] xercesc_2_7::IGXMLScanner::scanDocument(this = 0x107fcefb8, src =
> CLASS), line 213 in "IGXMLS
> [21] xercesc_2_7::SAXParser::parse(this = 0x107fcdd08, source = CLASS),
> line 544 in "SAXParser.cpp
>
> If you know regarding this problem please send me the details
> Thanks in advance
> -Riaj
>
--
This message is automatically gen
[jira] Updated: (XERCESC-1642) My application crashed on Solaris Sparc (64bit) using compiler CC(Sun C++ 5.5 Patch 113817-14 2005/07/19 ) and OS 5.8
[ http://issues.apache.org/jira/browse/XERCESC-1642?page=all ] Riaj Mohammed updated XERCESC-1642: --- Attachment: MemParse.tar attaching files -Riaj > My application crashed on Solaris Sparc (64bit) using compiler CC(Sun C++ 5.5 > Patch 113817-14 2005/07/19 ) and OS 5.8 > - > > Key: XERCESC-1642 > URL: http://issues.apache.org/jira/browse/XERCESC-1642 > Project: Xerces-C++ > Issue Type: Bug >Affects Versions: 2.7.0 > Environment: OS : SunOS 5.8 Generic_108528-24 sun4u sparc > SUNW,Sun-Fire-V440 Solaris > Compiler : CC: Sun C++ 5.5 Patch 113817-14 2005/07/19 > Xercers: xercesc_2_7 >Reporter: Riaj Mohammed >Priority: Critical > Attachments: MemParse.tar > > > I have build the xerces library successfully on solaris 64 bit, but at the > run time, I get a SIGBUS > > The stack trace is > > signal BUS (invalid address alignment) in realfree at 0x77d4a2ec > 0x77d4a2ec: realfree+0x0078:ldx [%i0 + 16], %o1 > Current function is xercesc_2_7::MemoryManagerImpl::deallocate >47 ::operator delete(p); > > > [1] realfree(0x107eb2524, 0x77ec1780, 0x107eb1990, > 0x77eb4f60, 0x107eb1980, 0xba7) > [2] _free_unlocked(0x77ec1668, 0x77eb4f60, 0x1080098b0, > 0x785069c4, 0x1080 > [3] free(0x1080098b0, 0x0, 0x106c5c460, 0x785069c4, > 0x7ef013c0, 0x0), at 0xfff > [4] operator delete(0x1080098b0, 0x106c5c4b0, 0xe, 0x785069c4, > 0x7f72c930, 0x0), a > =>[5] xercesc_2_7::MemoryManagerImpl::deallocate(this = 0x106c06b30, p = > 0x1080098b0), line 47 in "M > [6] xercesc_2_7::XMLBuffer::~XMLBuffer(this = 0x108009838), line 76 in > "XMLBuffer.hpp" > [7] xercesc_2_7::SchemaValidator::~SchemaValidator(this = 0x1080097d8), > line 340 in "SchemaValidat > [8] __SLIP.DELETER__L(0x1080097d8, 0x1, 0x7dc000e8, > 0x785069c4, 0x765f0024, 0x0), > [9] xercesc_2_7::IGXMLScanner::cleanUp(this = 0x1080043a8), line 559 in > "IGXMLScanner.cpp" > [10] xercesc_2_7::IGXMLScanner::~IGXMLScanner(this = 0x1080043a8), line 158 > in "IGXMLScanner.cpp" > [11] __SLIP.DELETER__P(0x1080043a8, 0x1, 0x7f72c930, > 0x7ef013c0, 0x7ef013c > [12] xercesc_2_7::AbstractDOMParser::cleanUp(this = 0x7ffedfb0), > line 160 in "AbstractDOMP > [13] xercesc_2_7::AbstractDOMParser::~AbstractDOMParser(this = > 0x7ffedfb0), line 128 in "A > [14] xercesc_2_7::XercesDOMParser::~XercesDOMParser(this = > 0x7ffedfb0), line 65 in "Xerces > [15] xercesc_2_7::XSDDOMParser::~XSDDOMParser(this = 0x7ffedfb0), > line 64 in "XSDDOMParser > [16] xercesc_2_7::IGXMLScanner::resolveSchemaGrammar(this = 0x107fcefb8, > loc = 0x107fd5fa0, uri = > [17] xercesc_2_7::IGXMLScanner::scanRawAttrListforNameSpaces(this = > 0x107fcefb8, attCount = 2), li > [18] xercesc_2_7::IGXMLScanner::scanStartTagNS(this = 0x107fcefb8, gotData > = true), line 2211 in " > [19] xercesc_2_7::IGXMLScanner::scanContent(this = 0x107fcefb8), line 889 > in "IGXMLScanner.cpp" > [20] xercesc_2_7::IGXMLScanner::scanDocument(this = 0x107fcefb8, src = > CLASS), line 213 in "IGXMLS > [21] xercesc_2_7::SAXParser::parse(this = 0x107fcdd08, source = CLASS), > line 544 in "SAXParser.cpp > > If you know regarding this problem please send me the details > Thanks in advance > -Riaj > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (XERCESC-1642) My application crashed on Solaris Sparc (64bit) using compiler CC(Sun C++ 5.5 Patch 113817-14 2005/07/19 ) and OS 5.8
[
http://issues.apache.org/jira/browse/XERCESC-1642?page=comments#action_12456810
]
Riaj Mohammed commented on XERCESC-1642:
Hi
Attached sample test case with xsd files in which I am getting SIGBUS/memory
alignment problem
Do the following changes in the Xerces C++ source file
\src\xerces-c\src\xercesc\sax\EntityResolver.hpp
InputSource*
SAXParser::resolveEntity( XMLResourceIdentifier* resourceIdentifier )
{
// Just map to the SAX entity resolver handler
if (fEntityResolver)
return
fEntityResolver->resolveEntity(resourceIdentifier->getPublicId(),
resourceIdentifier->getSystemId(),
resourceIdentifier->getBaseURI());
if (fXMLEntityResolver)
return fXMLEntityResolver->resolveEntity(resourceIdentifier);
return 0;
}
\src\xerces-c\src\xercesc\parsers\SAXParser.cpp
virtual InputSource* resolveEntity
(
const XMLCh* const publicId
, const XMLCh* const systemId
, const XMLCh* const baseURL = 0
) = 0;
Have done the above changes in the samples/MemParse to reproduce the problem
Enclosed tar files has the modified files
Steps to reproduce the problem
1)Copy the files to $XERCESROOT/samples/MemParse
2)Copy the xml_schem2.xsd to $XERCESROOT/bin
3) execute MemParse -v=never -n -s
Thnks
-riaj
> My application crashed on Solaris Sparc (64bit) using compiler CC(Sun C++ 5.5
> Patch 113817-14 2005/07/19 ) and OS 5.8
> -
>
> Key: XERCESC-1642
> URL: http://issues.apache.org/jira/browse/XERCESC-1642
> Project: Xerces-C++
> Issue Type: Bug
>Affects Versions: 2.7.0
> Environment: OS : SunOS 5.8 Generic_108528-24 sun4u sparc
> SUNW,Sun-Fire-V440 Solaris
> Compiler : CC: Sun C++ 5.5 Patch 113817-14 2005/07/19
> Xercers: xercesc_2_7
>Reporter: Riaj Mohammed
>Priority: Critical
>
> I have build the xerces library successfully on solaris 64 bit, but at the
> run time, I get a SIGBUS
>
> The stack trace is
>
> signal BUS (invalid address alignment) in realfree at 0x77d4a2ec
> 0x77d4a2ec: realfree+0x0078:ldx [%i0 + 16], %o1
> Current function is xercesc_2_7::MemoryManagerImpl::deallocate
>47 ::operator delete(p);
>
>
> [1] realfree(0x107eb2524, 0x77ec1780, 0x107eb1990,
> 0x77eb4f60, 0x107eb1980, 0xba7)
> [2] _free_unlocked(0x77ec1668, 0x77eb4f60, 0x1080098b0,
> 0x785069c4, 0x1080
> [3] free(0x1080098b0, 0x0, 0x106c5c460, 0x785069c4,
> 0x7ef013c0, 0x0), at 0xfff
> [4] operator delete(0x1080098b0, 0x106c5c4b0, 0xe, 0x785069c4,
> 0x7f72c930, 0x0), a
> =>[5] xercesc_2_7::MemoryManagerImpl::deallocate(this = 0x106c06b30, p =
> 0x1080098b0), line 47 in "M
> [6] xercesc_2_7::XMLBuffer::~XMLBuffer(this = 0x108009838), line 76 in
> "XMLBuffer.hpp"
> [7] xercesc_2_7::SchemaValidator::~SchemaValidator(this = 0x1080097d8),
> line 340 in "SchemaValidat
> [8] __SLIP.DELETER__L(0x1080097d8, 0x1, 0x7dc000e8,
> 0x785069c4, 0x765f0024, 0x0),
> [9] xercesc_2_7::IGXMLScanner::cleanUp(this = 0x1080043a8), line 559 in
> "IGXMLScanner.cpp"
> [10] xercesc_2_7::IGXMLScanner::~IGXMLScanner(this = 0x1080043a8), line 158
> in "IGXMLScanner.cpp"
> [11] __SLIP.DELETER__P(0x1080043a8, 0x1, 0x7f72c930,
> 0x7ef013c0, 0x7ef013c
> [12] xercesc_2_7::AbstractDOMParser::cleanUp(this = 0x7ffedfb0),
> line 160 in "AbstractDOMP
> [13] xercesc_2_7::AbstractDOMParser::~AbstractDOMParser(this =
> 0x7ffedfb0), line 128 in "A
> [14] xercesc_2_7::XercesDOMParser::~XercesDOMParser(this =
> 0x7ffedfb0), line 65 in "Xerces
> [15] xercesc_2_7::XSDDOMParser::~XSDDOMParser(this = 0x7ffedfb0),
> line 64 in "XSDDOMParser
> [16] xercesc_2_7::IGXMLScanner::resolveSchemaGrammar(this = 0x107fcefb8,
> loc = 0x107fd5fa0, uri =
> [17] xercesc_2_7::IGXMLScanner::scanRawAttrListforNameSpaces(this =
> 0x107fcefb8, attCount = 2), li
> [18] xercesc_2_7::IGXMLScanner::scanStartTagNS(this = 0x107fcefb8, gotData
> = true), line 2211 in "
> [19] xercesc_2_7::IGXMLScanner::scanContent(this = 0x107fcefb8), line 889
> in "IGXMLScanner.cpp"
> [20] xercesc_2_7::IGXMLScanner::scanDocument(this = 0x107fcefb8, src =
> CLASS), line 213 in "IGXMLS
> [21] xercesc_2_7::SAXParser::parse(this = 0x107fcdd08, source = CLASS),
> line 544 in "SAXParser.cpp
>
> If you know regarding this problem please send me the details
> Thanks in advance
> -Riaj
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues
[jira] Commented: (XERCESC-1642) My application crashed on Solaris Sparc (64bit) using compiler CC(Sun C++ 5.5 Patch 113817-14 2005/07/19 ) and OS 5.8
[
http://issues.apache.org/jira/browse/XERCESC-1642?page=comments#action_12456808
]
Riaj Mohammed commented on XERCESC-1642:
Hi
Attached sample test case with xsd files in which I am getting SIGBUS/memory
alignment problem
Do the following changes in the Xerces C++ source file
\src\xerces-c\src\xercesc\sax\EntityResolver.hpp
InputSource*
SAXParser::resolveEntity( XMLResourceIdentifier* resourceIdentifier )
{
// Just map to the SAX entity resolver handler
if (fEntityResolver)
return
fEntityResolver->resolveEntity(resourceIdentifier->getPublicId(),
resourceIdentifier->getSystemId(),
resourceIdentifier->getBaseURI());
if (fXMLEntityResolver)
return fXMLEntityResolver->resolveEntity(resourceIdentifier);
return 0;
}
\src\xerces-c\src\xercesc\parsers\SAXParser.cpp
virtual InputSource* resolveEntity
(
const XMLCh* constpublicId
, const XMLCh* constsystemId
, const XMLCh* constbaseURL = 0
) = 0;
Have done the above changes in the samples/MemParse to reproduce the problem
Enclosed tar files has the modified files
Steps to reproduce the problem
1)Copy the files to $XERCESROOT/samples/MemParse
2)Copy the xml_schem2.xsd to $XERCESROOT/bin
3) execute
> My application crashed on Solaris Sparc (64bit) using compiler CC(Sun C++ 5.5
> Patch 113817-14 2005/07/19 ) and OS 5.8
> -
>
> Key: XERCESC-1642
> URL: http://issues.apache.org/jira/browse/XERCESC-1642
> Project: Xerces-C++
> Issue Type: Bug
>Affects Versions: 2.7.0
> Environment: OS : SunOS 5.8 Generic_108528-24 sun4u sparc
> SUNW,Sun-Fire-V440 Solaris
> Compiler : CC: Sun C++ 5.5 Patch 113817-14 2005/07/19
> Xercers: xercesc_2_7
>Reporter: Riaj Mohammed
>Priority: Critical
>
> I have build the xerces library successfully on solaris 64 bit, but at the
> run time, I get a SIGBUS
>
> The stack trace is
>
> signal BUS (invalid address alignment) in realfree at 0x77d4a2ec
> 0x77d4a2ec: realfree+0x0078:ldx [%i0 + 16], %o1
> Current function is xercesc_2_7::MemoryManagerImpl::deallocate
>47 ::operator delete(p);
>
>
> [1] realfree(0x107eb2524, 0x77ec1780, 0x107eb1990,
> 0x77eb4f60, 0x107eb1980, 0xba7)
> [2] _free_unlocked(0x77ec1668, 0x77eb4f60, 0x1080098b0,
> 0x785069c4, 0x1080
> [3] free(0x1080098b0, 0x0, 0x106c5c460, 0x785069c4,
> 0x7ef013c0, 0x0), at 0xfff
> [4] operator delete(0x1080098b0, 0x106c5c4b0, 0xe, 0x785069c4,
> 0x7f72c930, 0x0), a
> =>[5] xercesc_2_7::MemoryManagerImpl::deallocate(this = 0x106c06b30, p =
> 0x1080098b0), line 47 in "M
> [6] xercesc_2_7::XMLBuffer::~XMLBuffer(this = 0x108009838), line 76 in
> "XMLBuffer.hpp"
> [7] xercesc_2_7::SchemaValidator::~SchemaValidator(this = 0x1080097d8),
> line 340 in "SchemaValidat
> [8] __SLIP.DELETER__L(0x1080097d8, 0x1, 0x7dc000e8,
> 0x785069c4, 0x765f0024, 0x0),
> [9] xercesc_2_7::IGXMLScanner::cleanUp(this = 0x1080043a8), line 559 in
> "IGXMLScanner.cpp"
> [10] xercesc_2_7::IGXMLScanner::~IGXMLScanner(this = 0x1080043a8), line 158
> in "IGXMLScanner.cpp"
> [11] __SLIP.DELETER__P(0x1080043a8, 0x1, 0x7f72c930,
> 0x7ef013c0, 0x7ef013c
> [12] xercesc_2_7::AbstractDOMParser::cleanUp(this = 0x7ffedfb0),
> line 160 in "AbstractDOMP
> [13] xercesc_2_7::AbstractDOMParser::~AbstractDOMParser(this =
> 0x7ffedfb0), line 128 in "A
> [14] xercesc_2_7::XercesDOMParser::~XercesDOMParser(this =
> 0x7ffedfb0), line 65 in "Xerces
> [15] xercesc_2_7::XSDDOMParser::~XSDDOMParser(this = 0x7ffedfb0),
> line 64 in "XSDDOMParser
> [16] xercesc_2_7::IGXMLScanner::resolveSchemaGrammar(this = 0x107fcefb8,
> loc = 0x107fd5fa0, uri =
> [17] xercesc_2_7::IGXMLScanner::scanRawAttrListforNameSpaces(this =
> 0x107fcefb8, attCount = 2), li
> [18] xercesc_2_7::IGXMLScanner::scanStartTagNS(this = 0x107fcefb8, gotData
> = true), line 2211 in "
> [19] xercesc_2_7::IGXMLScanner::scanContent(this = 0x107fcefb8), line 889
> in "IGXMLScanner.cpp"
> [20] xercesc_2_7::IGXMLScanner::scanDocument(this = 0x107fcefb8, src =
> CLASS), line 213 in "IGXMLS
> [21] xercesc_2_7::SAXParser::parse(this = 0x107fcdd08, source = CLASS),
> line 544 in "SAXParser.cpp
>
> If you know regarding this problem please send me the details
> Thanks in advance
> -Riaj
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur
