Hi Dave,
I tried with Xalan 1.3 / xlC5 /AIX 4.3.3.
I copied latest VariablesStack* files from cvs
and rebuilt the xalan.
I am able to reproduce the problem.
It dumps core with the same stack.
But it is working fine with TestXSLT(of xalan 1.2 also).
--Thanks
Raj..
> -----Original Message-----
> From: David N Bertoni/Cambridge/IBM [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, February 27, 2002 1:26 PM
> To: [EMAIL PROTECTED]
> Subject: RE: XalanC++ is Crashing for 470KB XML file.
>
>
> Hi Raj,
>
> Without a stylesheet and source file to test this with, there's nothing we
> can do to diagnose the problem. You might try running your stylesheet and
> source document through the Xalan 1.3 executables, just to see if you can
> reproduce this with them. If you can, please create a bug report and
> attach the documents. Unfortunately, we just don't have the resources to
> patch old versions of the code -- it's just too much work to do that.
>
> If you can't reproduce the problem with 1.3, you can always build Xerces
> 1.6.0 and Xalan 1.3 with xlC 3.6.6 -- there's no reason why it shouldn't
> work. Just get the source distributions and build the libraries yourself.
>
> Dave
>
>
>
>
>
> "Avula, Raj"
>
> <RAvula@firstam. To:
> "'[EMAIL PROTECTED]'"
> com> <[EMAIL PROTECTED]>
>
> cc: (bcc: David N
> Bertoni/Cambridge/IBM)
> 02/27/2002 12:16 Subject: RE: XalanC++ is
> Crashing for 470KB XML file.
> PM
>
> Please respond
>
> to xalan-dev
>
>
>
>
>
>
>
>
>
> Hi Dave,
> Thank you very much for the reply.
> I am using xalan 1.2 on AIX4.3.2 with xlC3.6.6.
> We are planning to move to xlC5 in future.
> But I have to get it working with the current compiler.
> I tried copying the latest files from cvs and re-builded xalan1.2.
> It is crashing for all the xml files.
> I also tried changing the VariablesStack::findXObject()
> method as suggested in the BUG#4506.
> It stills dumps core in my case.
> It would be great, If Can you please suggest a fix for me for xalan_1.2
>
>
> Thanks for the help.
> Raj..
>
>
> ...
>
>
> > -----Original Message-----
> > From: David N Bertoni/Cambridge/IBM
> [SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, February 26, 2002 7:33 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: XalanC++ is Crashing for 470KB XML file.
> >
> >
> > Hi Raj,
> >
> > This looks like this bug, which has already been fixed:
> >
> > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6506
> >
> > You can get a diff from CVS to patch your local copy. The files changed
> > were:
> >
> > xml-xalan/c/src/XSLT/VariablesStack.cpp
> > xml-xalan/c/src/XSLT/VariablesStack.hpp
> >
> > This doesn't have anything to do with the size of the input file --
> > Xalan-C
> > can process very large documents, provided you have adequate memory
> > available to the process.
> >
> > Dave
> >
> >
> > "Avula, Raj"
> >
> > <RAvula@firstam. To:
> > "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> >
> > com> cc: (bcc: David N
> > Bertoni/Cambridge/IBM)
> > Subject: XalanC++ is
> > Crashing for 470KB XML file.
> > 02/26/2002 05:13
> >
> > PM
> >
> > Please respond
> >
> > to xalan-dev
> >
> >
> > Hi,
> > Xalan is crashing for 470 KB input file. Here is the
> snippet
> > of
> > code, that I am using for transformation.
> > It is crashing in the axXalanTransformer.transform method.
> > Can you please go through it and let me know, If I can do any thing to
> get
> > away with this.
> > I am attaching the code at the end of the mail.
> >
> > Thanks for the help,
> > Raj..
> >
> > ...
> >
> >
>
>
>
>
"MMS <firstam.com>" made the following
annotations on 02/27/02 13:42:47
------------------------------------------------------------------------------
"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."
==============================================================================
