It looks like maybe an exception is being thrown while another exception is
active, which would explain the call to abort(). What platform/compiler
are you using? Is it AIX? Can you reproduce the problem on another
platform?
Dave
"Avula, Raj"
<RAvula@firstam. To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
com> cc:
Subject: RE: Corruption in
XalanOutputStreamPrintWriter.
12/28/2001 08:46
PM
Please respond
to xalan-dev
Here is the StackTrace.
IOT/Abort trap in signal.pthread_kill [/usr/lib/libpthreads.a] at
0xd03f4f14
($t
1)
0xd03f4f14 (pthread_kill+0x80) 80410014 lwz r2,0x14(r1)
(dbxlarge) where
signal.pthread_kill(??, ??) at 0xd03f4f14
signal._p_raise(??) at 0xd03f44ac
raise.raise(??) at 0xd0013bec
abort.abort() at 0xd000d350
terminate__Fv() at 0xd03b3b28
invokedtr.__Invoke__Destructor() at 0xdae2b84c
except.__DoThrow() at 0xdae2b494
doFlush__20XalanStdOutputStreamFv() at 0xdaf35cc4
flush__28XalanOutputStreamPrintWriterFv() at 0xdaf33148
close__28XalanOutputStreamPrintWriterFv() at 0xdaf330f0
endDocument__15FormatterToTextFv() at 0xdae8c0d8
endDocument__14XSLTEngineImplFv() at 0xdaec8010
endDocument__33StylesheetExecutionContextDefaultFv() at 0xdaeb278c
process__14StylesheetRootCFP9XalanNodeR16XSLTResultTargetR26StylesheetExecut
ionC
ontext() at 0xdaed9f48
process__14XSLTEngineImplFRC15XSLTInputSourceR16XSLTResultTargetR26Styleshee
tExe
cutionContext() at 0xdaec1d70
transform__16XalanTransformerFRC17XalanParsedSourcePC23XalanCompiledStyleshe
etRC
16XSLTResultTarget() at 0xdaf8f01c
transform__16XalanTransformerFRC15XSLTInputSourcePC23XalanCompiledStylesheet
RC16
XSLTResultTarget() at 0xdaf8f7a8
unnamed block $b1187, line 114 in "CXSTransformImpl.cc"
> -----Original Message-----
> From: Avula, Raj
> Sent: Friday, December 28, 2001 5:13 PM
> To: '[EMAIL PROTECTED]'
> Subject: Corruption in XalanOutputStreamPrintWriter.
>
>
> Hi,
> transform method of XalanTransformer failing if I use ostrstream to
> create XSLTResultTarget for the
> attached xml, xsl files. The problem goes away if one or more characters
> are
> added or deleted to xml or xsl.
> And If I use DOMStringPrintWriter it works fine. I am attaching xml, xsl
,
> .cc files.
> Did any body face this kind of problem before? Please let me know.
>
> Thanks,
> Raj..
>
> <<Temp.xml>> <<temp.xsl>> <<XalanTransform.cpp>>
>
> "MMS <firstam.com>" made the following
> annotations on 12/28/01 17:15:02
>
--------------------------------------------------------------------------
> ----
> "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."
>
>
==========================================================================
> ==== << File: Temp.xml >> << File: temp.xsl >> << File:
> XalanTransform.cpp >>
"MMS <firstam.com>" made the following
annotations on 12/28/01 17:47:44
------------------------------------------------------------------------------
"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."
==============================================================================
