- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- core dump in HPMutexWrapper::~HPMutexWrapper()
Operating System - HP-UX
1752618
Members
4753
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2004 11:34 AM
тАО10-29-2004 11:34 AM
core dump in HPMutexWrapper::~HPMutexWrapper()
I got a core dump while starting our application on HP 11.00:
(gdb) run
Starting program: /usr/netiq/UnixAgent/bin/./agent
Program received signal SIGSEGV, Segmentation fault.
0x6faae718 in pthread_mutex_destroy () from /usr/lib/libpthread.1
(gdb) where
#0 0x6faae718 in pthread_mutex_destroy () from /usr/lib/libpthread.1
#1 0x6fbdccb8 in __thread_mutex_free () from /usr/lib/libc.2
#2 0x6ff3e470 in _HPMutexWrapper::~_HPMutexWrapper ()
from /usr/lib/libstd_v2.2
#3 0x6efc10c4 in __dt__Q2_4__rw12__string_refXTcTQ2_3std11char_traitsXTc_TQ2_3std9allocatorXTc__Fv ()
from /home/ilin/src/sjc/sjcunixdepot/main/lib/agentC/hpux/libNqUA.sl
#4 0x6efc0a48 in std::basic_string,std::allocator >::_C_getRep (this=0x6fff11f0, __cap=128, __len=1)
at /opt/aCC/include_std/string.cc:70
#5 0x6feab8b8 in __ct__Q2_3std12basic_stringXTcTQ2_3std11char_traitsXTc_TQ2_3std9allocatorXTc__FPCcRCQ2_3std9allocatorXTc__2 () from /usr/lib/libstd_v2.2
#6 0x6ff07a08 in std::locale::name () from /usr/lib/libstd_v2.2
#7 0x6feaabd0 in _C_initfacet__Q2_3std5ctypeXTc_FRCQ2_3std6locale ()
from /usr/lib/libstd_v2.2
#8 0x6ff081ec in std::locale::_C_install_facet () from /usr/lib/libstd_v2.2
#9 0x6ff07f64 in std::locale::_C_make_facet () from /usr/lib/libstd_v2.2
#10 0x6ff027cc in std::ios_base::Init::Init () from /usr/lib/libstd_v2.2
#11 0x6ef996d8 in __sinit_nqext_callbacks_cpp___3stdFv ()
from /home/ilin/src/sjc/sjcunixdepot/main/lib/agentC/hpux/libNqUA.sl
#12 0x6fde1b54 in __shlInit () from /usr/lib/libCsup_v2.2
#13 0x6ef87788 in _shlInit ()
from /home/ilin/src/sjc/sjcunixdepot/main/lib/agentC/hpux/libNqUA.sl
---Type to continue, or q to quit---
#14 0x6fde1548 in __shlinit () from /usr/lib/libCsup_v2.2
#15 0x6fde3b40 in _main () from /usr/lib/libCsup_v2.2
This occurs only on HP boxes with B.11.00 900/785 2012304306. The HP boxes with B.11.00 900/785 2004313874 or 11.11 started our application successfully.
Our application used HP ANSI C++ compiler (aCC) B3910B A.03.33 with following linkage options:
-lcl -lnsl -lnm -lmalloc -ldld -lm -lcrypt -lsec -lpthread -lc -lcrypto -lCsup_v2 -lstd_v2
I notices library size differences for libCsup_v2.2:
11.00/2012304306 11.00/2004313874
====================================
217088 208896
What can I do to resolve the issue?
Isabel Lin
(gdb) run
Starting program: /usr/netiq/UnixAgent/bin/./agent
Program received signal SIGSEGV, Segmentation fault.
0x6faae718 in pthread_mutex_destroy () from /usr/lib/libpthread.1
(gdb) where
#0 0x6faae718 in pthread_mutex_destroy () from /usr/lib/libpthread.1
#1 0x6fbdccb8 in __thread_mutex_free () from /usr/lib/libc.2
#2 0x6ff3e470 in _HPMutexWrapper::~_HPMutexWrapper ()
from /usr/lib/libstd_v2.2
#3 0x6efc10c4 in __dt__Q2_4__rw12__string_refXTcTQ2_3std11char_traitsXTc_TQ2_3std9allocatorXTc__Fv ()
from /home/ilin/src/sjc/sjcunixdepot/main/lib/agentC/hpux/libNqUA.sl
#4 0x6efc0a48 in std::basic_string
at /opt/aCC/include_std/string.cc:70
#5 0x6feab8b8 in __ct__Q2_3std12basic_stringXTcTQ2_3std11char_traitsXTc_TQ2_3std9allocatorXTc__FPCcRCQ2_3std9allocatorXTc__2 () from /usr/lib/libstd_v2.2
#6 0x6ff07a08 in std::locale::name () from /usr/lib/libstd_v2.2
#7 0x6feaabd0 in _C_initfacet__Q2_3std5ctypeXTc_FRCQ2_3std6locale ()
from /usr/lib/libstd_v2.2
#8 0x6ff081ec in std::locale::_C_install_facet () from /usr/lib/libstd_v2.2
#9 0x6ff07f64 in std::locale::_C_make_facet () from /usr/lib/libstd_v2.2
#10 0x6ff027cc in std::ios_base::Init::Init () from /usr/lib/libstd_v2.2
#11 0x6ef996d8 in __sinit_nqext_callbacks_cpp___3stdFv ()
from /home/ilin/src/sjc/sjcunixdepot/main/lib/agentC/hpux/libNqUA.sl
#12 0x6fde1b54 in __shlInit () from /usr/lib/libCsup_v2.2
#13 0x6ef87788 in _shlInit ()
from /home/ilin/src/sjc/sjcunixdepot/main/lib/agentC/hpux/libNqUA.sl
---Type
#14 0x6fde1548 in __shlinit () from /usr/lib/libCsup_v2.2
#15 0x6fde3b40 in _main () from /usr/lib/libCsup_v2.2
This occurs only on HP boxes with B.11.00 900/785 2012304306. The HP boxes with B.11.00 900/785 2004313874 or 11.11 started our application successfully.
Our application used HP ANSI C++ compiler (aCC) B3910B A.03.33 with following linkage options:
-lcl -lnsl -lnm -lmalloc -ldld -lm -lcrypt -lsec -lpthread -lc -lcrypto -lCsup_v2 -lstd_v2
I notices library size differences for libCsup_v2.2:
11.00/2012304306 11.00/2004313874
====================================
217088 208896
What can I do to resolve the issue?
Isabel Lin
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2004 08:36 PM
тАО11-01-2004 08:36 PM
Re: core dump in HPMutexWrapper::~HPMutexWrapper()
Hello Isabel,
have you consistenly compiled all your objects and linked them with -mt option?
Regards
Cyrille
PS: also, if you are doing STLv2 stuff, you should not be specifyinh all these libs on the link line. Just add -AA at compile time and link time.
-lpthread will be implicitely added by -mt.
PS: aCC3.33 is very old, you just upgrade to latest compiler...
For reference
http://h21007.www2.hp.com/dspp/ml/showArchiveMessage/1,,24!03!07!0050,00.html
http://h21007.www2.hp.com/dspp/ml/showArchiveMessage/1,,24!03!06!0089,00.html
have you consistenly compiled all your objects and linked them with -mt option?
Regards
Cyrille
PS: also, if you are doing STLv2 stuff, you should not be specifyinh all these libs on the link line. Just add -AA at compile time and link time.
-lpthread will be implicitely added by -mt.
PS: aCC3.33 is very old, you just upgrade to latest compiler...
For reference
http://h21007.www2.hp.com/dspp/ml/showArchiveMessage/1,,24!03!07!0050,00.html
http://h21007.www2.hp.com/dspp/ml/showArchiveMessage/1,,24!03!06!0089,00.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2004 08:44 PM
тАО11-01-2004 08:44 PM
Re: core dump in HPMutexWrapper::~HPMutexWrapper()
Have you compiled on each system, or compiled on one, and copy binaries ?
Regards,
Fred
Regards,
Fred
--
"Reality is just a point of view." (P. K. D.)
"Reality is just a point of view." (P. K. D.)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP