Yup, this has been fixed in the latest CVS code.  Here's the diff:

   cvs diff -r 1.50 -r 1.49 XPathProcessorImpl.cpp (in directory V:
   \xml-xalan\c\src\XPath\)
   Index: XPathProcessorImpl.cpp
   ===================================================================
   RCS file: /home/cvspublic/xml-xalan/c/src/XPath/XPathProcessorImpl.cpp,v
   retrieving revision 1.50
   retrieving revision 1.49
   diff -r1.50 -r1.49
   502c502
   <              m_expression->adjustPattern(m_expression->patternMapSize
   () - 1,
   ---
   >              m_expression->adjustPattern(m_expression->patternMapSize
   (),

   *****CVS exited normally with code 1*****

Dave



                                                                                       
                                                           
                      "Avula, Raj"                                                     
                                                           
                      <RAvula@firstam.         To:      "'[EMAIL PROTECTED]'" 
<[EMAIL PROTECTED]>                                   
                      com>                     cc:      (bcc: David N 
Bertoni/Cambridge/IBM)                                                      
                                               Subject: Xalan Core dumps in 
XPathExpression::adjustPattern.                                       
                      03/21/2002 05:32                                                 
                                                           
                      PM                                                               
                                                           
                      Please respond                                                   
                                                           
                      to xalan-dev                                                     
                                                           
                                                                                       
                                                           
                                                                                       
                                                           





Hi,
             Xalan1.3 dumps core in XPathExpression::adjustPattern. (xlc5 &
aix433)
I have checked this function adding some debug messages.
I observed that theIndex & m_patternMap.size() is always same.
I that case the [] operator of vector always return some invalid value.
Please bear with me, if any of my comments are invalid.

       void
        adjustPattern(
                        OpCodeMapSizeType       theIndex,
                        PatternMapValueType     theAdjustment)
        {
               m_patternMap[theIndex] += theAdjustment;
        }

Thanks,
Raj..

Here is the core.

mapPatternElemPos__18XPathProcessorImplCFibT2() at 0xd82a180c
tokenize__18XPathProcessorImplFRC14XalanDOMStringPQ2_3std6vectorXT14XalanDOM

StringTQ2_3std9allocatorXT14XalanDOMString__() at 0xd82a082c
initXPath__18XPathProcessorImplFR5XPathRC14XalanDOMStringRC14PrefixResolverP

C7Locator() at 0xd82a03a0
createXPath__36StylesheetConstructionContextDefaultFPC7LocatorRC14XalanDOMSt

ringRC14PrefixResolver() at 0xd8355178
createXPath__36StylesheetConstructionContextDefaultFPC7LocatorPCUsRC14Prefix

Resolver() at 0xd8355224
__ct__8ElemWhenFR29StylesheetConstructionContextR10StylesheetRC13AttributeLi

stiT4() at 0xd82630b0
startElement__17StylesheetHandlerFCPCUsR13AttributeList() at 0xd81c0df8
startElement__9SAXParserFRC14XMLElementDeclCUiCPCUsRC11RefVectorOfXT7XMLAttr

_CUiCbCb() at 0xd799159c
scanStartTag__10XMLScannerFRb() at 0xd78a3158
scanContent__10XMLScannerFCb() at 0xd789f014
scanDocument__10XMLScannerFRC11InputSourceCb() at 0xd789e210
parse__9SAXParserFRC11InputSourceCb() at 0xd7990540
parseXMLStream__19XercesParserLiaisonFRC11InputSourceR15DocumentHandlerRC14X

alanDOMString() at 0xd80d29b4
XalanSourceTreeParserLiaison.parseXMLStream(const
InputSource&,DocumentHandler&,const XalanDOMString&)(??, ??, ??, ??), line
213 in "XalanSourceTreeParserLiaison.cpp"
parseXML__14XSLTEngineImplFRC11InputSourceP15DocumentHandlerP13XalanDocument

() at 0xd828841c
parseXML__14XSLTEngineImplFRC14XalanDOMStringP15DocumentHandlerP13XalanDocum

ent() at 0xd828818c
parseXML__36StylesheetConstructionContextDefaultFRC14XalanDOMStringP15Docume

ntHandlerP13XalanDocument() at 0xd8355394
processImport__17StylesheetHandlerFPCUsRC13AttributeListPC7Locator() at
0xd81c4838
processTopLevelElement__17StylesheetHandlerFPCUsRC14XalanDOMStringRC14XalanD

OMStringRC13AttributeListiPC7LocatorRbT7() at 0xd81c2644
startElement__17StylesheetHandlerFCPCUsR13AttributeList() at 0xd81c0874
startElement__9SAXParserFRC14XMLElementDeclCUiCPCUsRC11RefVectorOfXT7XMLAttr

_CUiCbCb() at 0xd799159c
scanStartTag__10XMLScannerFRb() at 0xd78a3158
scanContent__10XMLScannerFCb() at 0xd789f014
scanDocument__10XMLScannerFRC11InputSourceCb() at 0xd789e210
parse__9SAXParserFRC11InputSourceCb() at 0xd7990540
parseXMLStream__19XercesParserLiaisonFRC11InputSourceR15DocumentHandlerRC14X

alanDOMString() at 0xd80d29b4
XalanSourceTreeParserLiaison.parseXMLStream(const
InputSource&,DocumentHandler&,const XalanDOMString&)(??, ??, ??, ??), line
213 in "XalanSourceTreeParserLiaison.cpp"
processStylesheet__14XSLTEngineImplFRC15XSLTInputSourceR29StylesheetConstruc

tionContext() at 0xd8287af0
compileStylesheet__FRC15XSLTInputSourceR14XSLTEngineImplR36StylesheetConstru

ctionContextDefaultP12ErrorHandlerP14EntityResolver() at 0xd837af7c
__ct__30XalanCompiledStylesheetDefaultFRC15XSLTInputSourceR30XSLTProcessorEn

vSupportDefaultR14XSLTEngineImplP12ErrorHandlerP14EntityResolver() at
0xd837add0
compileStylesheet__16XalanTransformerFRC15XSLTInputSourceRPC23XalanCompiledS

tylesheet() at 0xd836db4c
unnamed block $b13, line 79 in "CTransformImpl.cc"

"MMS <firstam.com>" made the following
 annotations on 03/21/02 17:34:05
------------------------------------------------------------------------------

"THIS E-MAIL MESSAGE AND ANY FILES TRANSMITTED HEREWITH, ARE INTENDED
SOLELY FOR THE USE OF THE INDIVIDUAL(S) ADDRESSED AND MAY CONTAIN
CONFIDENTIAL, PROPRIETARY OR PRIVILEGED INFORMATION.  IF YOU ARE NOT THE
ADDRESSEE INDICATED IN THIS MESSAGE (OR RESPONSIBLE FOR DELIVERY OF THIS
MESSAGE TO SUCH PERSON) YOU MAY NOT REVIEW, USE, DISCLOSE OR DISTRIBUTE
THIS MESSAGE OR ANY FILES TRANSMITTED HEREWITH.  IF YOU RECEIVE THIS
MESSAGE IN ERROR, PLEASE CONTACT THE SENDER BY REPLY E-MAIL AND DELETE THIS
MESSAGE AND ALL COPIES OF IT FROM YOUR SYSTEM."

==============================================================================







Reply via email to