Re: Crash in Xerces 2.1.0

2002-11-19 Thread oliver . white
(bcc: David N Bertoni/Cambridge/IBM) 11/19/2002 03:31 Subject: Re: Crash in Xerces 2.1.0 PM Please respond to xerces-c-dev Ok... strange one... Is there any constraints regarding linking

Re: Crash in Xerces 2.1.0

2002-11-19 Thread David N Bertoni/Cambridge/IBM
EMAIL PROTECTED] cc: (bcc: David N Bertoni/Cambridge/IBM) 11/19/2002 03:31 Subject: Re: Crash

Re: Crash in Xerces 2.1.0

2002-11-19 Thread oliver . white
] cc: 11/20/02 09:14 Fax to: AM Subject: Re: Crash in Xerces 2.1.0

Re: Crash in Xerces 2.1.0

2002-11-19 Thread David N Bertoni/Cambridge/IBM
] cc: (bcc: David N Bertoni/Cambridge/IBM) 11/19/2002 02:17 Subject: Re: Crash in Xerces 2.1.0

Re: Crash in Xerces 2.1.0

2002-11-19 Thread oliver . white
m> Fax to: Subject: Re: Crash in Xerces 2.1.0 11

Re: Crash in Xerces 2.1.0

2002-11-19 Thread oliver . white
cc: Fax to: 11/19/02 07:38 Subject: Re: Crash in Xerces 2.1.0

Re: Crash in Xerces 2.1.0

2002-11-19 Thread Alberto Massari
At 15.47 19/11/2002 +1100, you wrote: Hi folks. I've got a strange error that keeps cropping up, using Xalan. The code below crashes on the transform line, and the error seems to be deep in the bowels of Xerces, according to the stack trace. I'm using xalan 1.4.0 with xerces 2.1.0. If you have an

Re: Crash in Xerces 2.1.0

2002-11-19 Thread Gareth Reakes
Hi, what is the error? Gareth On Tue, 19 Nov 2002 [EMAIL PROTECTED] wrote: > Hi folks. I've got a strange error that keeps cropping up, using Xalan. The > code below crashes on the transform line, and the error seems to be deep in > the bowels of Xerces, according to the stack trace. I'm

Re: Crash in Xerces 2.1.0

2002-11-18 Thread oliver . white
I should have mentioned... I'm running under NT 4.0. -- Oli White - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Crash in Xerces 2.1.0

2002-11-18 Thread oliver . white
Hi folks. I've got a strange error that keeps cropping up, using Xalan. The code below crashes on the transform line, and the error seems to be deep in the bowels of Xerces, according to the stack trace. I'm using xalan 1.4.0 with xerces 2.1.0. If you have any ideas as to what might be causing the