Hi Boris,
I am very sorry for the delay in responding to you. And Thanks a lot to
you, as your comment helped me to resolve this problem.
Yes our application is multi-threaded. But the concurrency of initialize()
and terminate() being invoked concurrently is almost not possible
logically, as we call initialize() and terminate() sequentially in each
thread. And also locking mechanism is in place to avoid the concurrent
access to those methods.
However I also agree to the point that there is some problem with threading
here. The reason being when I linked my application with libmtmalloc.so,
this problem has not surfaced at all since then. I am being able to
reliably process the request multiple times.
Thanks a million again for your guidance when I required that the most.
Regards
Debi Prasad Mishra
From: Boris Kolpackov <bo...@codesynthesis.com>
To: c-users@xerces.apache.org
Date: 29/04/2009 02:10
Subject: Re: Xerces 3.0.0 core dump in IGXMLScanner (same request does not
core dump each time)
Hi Debi,
Debi P Mishra1 <dpmis...@in.ibm.com> writes:
> And one more observation is when we put sleep of 1 sec before triggering
> each request this goes fine. But when there is no gap, it core dumps
after
> processing certain request. And how many request it is going to process
> is also not certain.
Is your application multi-threaded? If so, do you call Initialize() and
Terminate() from several threads potentially concurrently?
Boris
--
Boris Kolpackov, Code Synthesis Tools
http://codesynthesis.com/~boris/blog
Open source XML data binding for C++:
http://codesynthesis.com/products/xsd
Mobile/embedded validating XML parsing:
http://codesynthesis.com/products/xsde
