- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SIGSEGV in __exit_handler ()
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО09-09-2009 02:59 AM
тАО09-09-2009 02:59 AM
I've got an enormous error while shutting down my application on HP-UX B.11.31 U ia64 machine, while it works fine on HP-UX B.11.23 U ia64.
The gdb's message is:
Program received signal SIGSEGV, Segmentation fault
si_code: 1 - SEGV_MAPERR - Address not mapped to object.
0x9ffffffffb07dce0:0 in __exit_handler ()
at ../../../../../core/libs/libc/shared_em_64_perf/../core/gen/exit.c:374
374 ../../../../../core/libs/libc/shared_em_64_perf/../core/gen/exit.c: No such file or directory.
in ../../../../../core/libs/libc/shared_em_64_perf/../core/gen/exit.c
I've noticed that /lib/hpux64/libc.so.1 differs in these machines, but stood equal by name... ``strings'' says that:
11.31 has: $ B.11.31 Jun 5 2009 01:24:39 $ date stamp, while
11.23 has: $ PATCH_11.23/PHCO_36673 Aug 7 2007 02:44:44 $
Can anyone help me with the problem identification?
Solved! Go to Solution.
- Tags:
- SIGSEGV
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2009 04:32 AM
тАО09-09-2009 04:32 AM
Re: SIGSEGV in __exit_handler ()
(gdb) disas $pc-16*12 $pc+16*4
(gdb) info reg
(gdb) bt
>I've noticed that /lib/hpux64/libc.so.1 differs in these machines
Naturally, that's why one is 11.23 and the other is 11.31. ;-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2009 06:35 AM
тАО09-09-2009 06:35 AM
Re: SIGSEGV in __exit_handler ()
>>I've noticed that /lib/hpux64/libc.so.1 differs in these machines
>Naturally, that's why one is 11.23 and the other is 11.31. ;-)
Why not differ in names? :-|
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2009 12:18 AM
тАО09-10-2009 12:18 AM
Re: SIGSEGV in __exit_handler ()
(The implicit offer was to provide it and I would make suggestions.)
>Why not differ in names?
Since HP-UX is forward compatible, why keep an obsolete 11.23 libc on a 11.31 system?
Only 10.20 libs are kept with the previous name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2009 04:14 AM
тАО09-10-2009 04:14 AM
Re: SIGSEGV in __exit_handler ()
Seems to be a problem in your application. Did you control the options used at compile time witch can give problem for the linker !
Need more info to go ahead (compiler, language, ...).
Look also, if you have not side effect in the source code ... It will be hard to find out !
Good Luck,
Roland
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2009 12:07 AM
тАО09-11-2009 12:07 AM
Re: SIGSEGV in __exit_handler ()
This is the standard's weak point in scoped static class elements and dlclose():
http://www.sourceware.org/ml/libc-alpha/1999-q1/msg00273.html
Don't anybody knows some workaround for this?
- Tags:
- dlclose
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2009 04:27 AM
тАО09-11-2009 04:27 AM
Re: SIGSEGV in __exit_handler ()
http://www.sourceware.org/ml/libc-alpha/1999-q1/msg00273.html
dlclose is not part of the C++ Standard.
>Don't anybody know some workaround for this?
What compiler are you using? aC++ should handle this.
Do you have a stack trace?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2009 04:45 AM
тАО09-11-2009 04:45 AM
Re: SIGSEGV in __exit_handler ()
But I ought to compile the code with gcc and link it with HPUX ld, and they don't understand each other in the implementation of the 3.3.5.3 Runtime API (it seems so, I'm not sure)... please see http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1370786 for the example.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2009 04:55 AM
тАО09-11-2009 04:55 AM
Re: SIGSEGV in __exit_handler ()
You must compile with g++. And NOT link directly with ld but use g++ to link.
>they don't understand each other in the implementation of the 3.3.5.3 Runtime API
The linker knows nothing about anything C++. This must be done in the C++ runtime lib.
And with aC++, we take a stick to dld to make sure everything works. :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2009 05:02 AM
тАО09-11-2009 05:02 AM
Re: SIGSEGV in __exit_handler ()
>You must compile with g++. And NOT link directly with ld but use g++ to link.
Yes-yes, I mean that, calling gcc as a common name ;).. compiled and linked via ``g++'' command, but it is configured to use --with-ld=/usr/ccs/bin/ld...
>>they don't understand each other in the implementation of the 3.3.5.3 Runtime API
>The linker knows nothing about anything C++. This must be done in the C++ runtime lib.
Yes, no C++ -- I agree, but due to the Itanuim C++ ABI section 3.3.5.3 "C" we have:
"When linking any DSO containing a call to __cxa_atexit, the linker should define a hidden symbol __dso_handle, with a value which is an address in one of the object's segments." This must be done in linktime ;)
>And with aC++, we take a stick to dld to make sure everything works. :-)
?