You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by Boris Kolpackov <bo...@codesynthesis.com> on 2007/01/30 08:11:54 UTC
Re: The xerces 2.5 library for HPUX IA 32 bit is core dumping
Hi,
"K, Dhevendran (OpenView, Teleco)" <dk...@hp.com> writes:
> #17 0x60000000cc62b9e0:0 in
> xercesc_2_5::DOM_Document::~DOM_Document()+0x20 () at
> /XERCES_25/xerces-c-src_2_5_0/src/xercesc/dom/deprecated/DOM_Document.cp
> p:89
> #18 0x60000000c96d4a30:0 in _ZN10TXMLHelperD9Ev () at
> ../TXMLHelper.cc:96
> #19 0x60000000c96d5250:0 in TXMLHelper::~TXMLHelper()+0x30 () at
> nl_TXMLHelper.cc:0
> #20 0x60000000c99b67f0:0 in _ZN11TCfgBuilderD9Ev () at
> /opt/aCC/include_std/string:995
> #21 0x60000000c99b4550:0 in TCfgBuilder::~TCfgBuilder()+0x30 () from
> /opt/OV/TeOVO/lib/libovtiocfg.3
> #22 0x4017250:0 in
> TSingleton<TCfgBuilder,TGuard,TMutex>::Destroyer::~Destroyer()+0x90 ()
> #23 0x60000000c0b92660:0 in __cxa_finalize+0x1d0 () from
> /usr/lib/hpux32/libCsup.so.1
> #24 0x60000000c0b98770:0 in __cxxTerm_body+0x180 () from
> /usr/lib/hpux32/libCsup.so.1
> #25 0x60000000c0b988c0:0 in __cxxTerm+0x20 () from
> /usr/lib/hpux32/libCsup.so.1
> #26 0x60000000c0295ec0:0 in __exit_handler+0xa0 () from
> /usr/lib/hpux32/libc.so.1
>From the stack trace above it appears that you are releasing the DOM
document via static instance destruction, after main() has terminated.
I think the most likely cause of the core dump is that you've already
called XMLPlatformUtils::Terminate().
hth,
-boris
--
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: The xerces 2.5 library for HPUX IA 32 bit is core dumping
Posted by Boris Kolpackov <bo...@codesynthesis.com>.
Hi,
"K, Dhevendran (OpenView, Teleco)" <dk...@hp.com> writes:
> Is there any reason for this?
This probably resulted in a memory corruption which often manifests
itself differently on different platforms.
> Will there be any system resource leak
> (like memory/handler/semaphore/shared memory/..etc ) if I remove this
> call ?
I don't think so if your application is terminating anyway. Though it
would be cleaner to have the call to terminate after releasing all
Xercec-C++ resources.
hth,
-boris
--
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
RE: Re: The xerces 2.5 library for HPUX IA 32 bit is core dumping
Posted by "K, Dhevendran (OpenView, Teleco)" <dk...@hp.com>.
Hi
Thanks a lot for your reply :) After removing the explicit call of the
API XMLPlatformUtils::Terminate() from my application, it is NOT core
dumping :)
This is the legacy code, in one of our class ( which is neither not
static class nor its instance ), in the constructer the API
XMLPlatformUtils::Initialize() is explicitly called and in the
destructor, the API XMLPlatformUtils::Terminate() is explicitly called.
I am surprising to see core dump only in HP-UX IA (But, not in HP-UX PA
). Is there any reason for this? Will there be any system resource leak
(like memory/handler/semaphore/shared memory/..etc ) if I remove this
call ?
Thanks in Advance
With Warm Regards,
Dheva
-----Original Message-----
From: Boris Kolpackov [mailto:boris@codesynthesis.com]
Sent: Tuesday, January 30, 2007 12:42 PM
To: c-dev@xerces.apache.org
Subject: Re: The xerces 2.5 library for HPUX IA 32 bit is core dumping
Hi,
"K, Dhevendran (OpenView, Teleco)" <dk...@hp.com> writes:
> #17 0x60000000cc62b9e0:0 in
> xercesc_2_5::DOM_Document::~DOM_Document()+0x20 () at
> /XERCES_25/xerces-c-src_2_5_0/src/xercesc/dom/deprecated/DOM_Document.
> cp
> p:89
> #18 0x60000000c96d4a30:0 in _ZN10TXMLHelperD9Ev () at
> ../TXMLHelper.cc:96
> #19 0x60000000c96d5250:0 in TXMLHelper::~TXMLHelper()+0x30 () at
> nl_TXMLHelper.cc:0 #20 0x60000000c99b67f0:0 in _ZN11TCfgBuilderD9Ev ()
> at
> /opt/aCC/include_std/string:995
> #21 0x60000000c99b4550:0 in TCfgBuilder::~TCfgBuilder()+0x30 () from
> /opt/OV/TeOVO/lib/libovtiocfg.3
> #22 0x4017250:0 in
> TSingleton<TCfgBuilder,TGuard,TMutex>::Destroyer::~Destroyer()+0x90 ()
> #23 0x60000000c0b92660:0 in __cxa_finalize+0x1d0 () from
> /usr/lib/hpux32/libCsup.so.1
> #24 0x60000000c0b98770:0 in __cxxTerm_body+0x180 () from
> /usr/lib/hpux32/libCsup.so.1
> #25 0x60000000c0b988c0:0 in __cxxTerm+0x20 () from
> /usr/lib/hpux32/libCsup.so.1
> #26 0x60000000c0295ec0:0 in __exit_handler+0xa0 () from
> /usr/lib/hpux32/libc.so.1
>From the stack trace above it appears that you are releasing the DOM
document via static instance destruction, after main() has terminated.
I think the most likely cause of the core dump is that you've already
called XMLPlatformUtils::Terminate().
hth,
-boris
--
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org