topic Re: signal 11 when linking c++ binary in Operating System - HP-UX

signal 11 when linking c++ binary

Nagarajan Ragunathan — Tue, 05 Apr 2005 17:59:19 GMT

when linking a C++ binary, getting the following error:

ucomp :
Error : Unexpected signal 11 received. See signal(2) or contact HP if you did not intentionally send this signal. (6987)

any ideas or how to resolve this ?
doing the build on HP 11.11 system.

Thanks

Re: signal 11 when linking c++ binary

A. Clay Stephenson — Tue, 05 Apr 2005 18:08:15 GMT

Signal 11 (SIGSEGV) is a segmentation violation. It could be a bug in the linker ld OR you may simply need to increase maxdsiz and/or maxssiz. Increase maxssiz to something around 64MB (and that is generous) and maxdsiz to somewhere between 256MB and 1GB. I would also look for and install and ld/as/cc related patches.

Re: signal 11 when linking c++ binary

Nagarajan Ragunathan — Tue, 05 Apr 2005 18:28:30 GMT

I have the following values set.
maxdsiz 0xb0000000 - 0XB0000000
maxdsiz_64bit 0x400000000 - 0X400000000
maxssiz 0x8000000 - 0X8000000
maxssiz_64bit 0x10000000 - 0X10000000

any specific ld patch to be checked ?
I will also search to see any patch related to this.

Thanks

Re: signal 11 when linking c++ binary

Ermin Borovac — Wed, 06 Apr 2005 01:43:55 GMT

Please check the version of Auxiliary-Opt.LANG-AUX fileset

# swlist -l fileset | grep Auxiliary-Opt.LANG-AUX

If the version is 11.11.06 install the following patches.

Patch Name: PHSS_28594
Patch Description: s700_800 11.X +O4/PBO Compiler B.11.11.06 cumulative patch

Patch Name: PHSS_28706
Patch Description: s700_800 11.X ANSI C compiler B.11.11.06 cumulative patch

From patch notes

JAGae35670 : AR0902 ucomp generates error in ld -r phase (6987)

Re: signal 11 when linking c++ binary

Nagarajan Ragunathan — Wed, 06 Apr 2005 12:57:47 GMT

I have 11.11.08 version.

$ swlist -l fileset | grep Auxiliary-Opt.LANG-AUX
Auxiliary-Opt.LANG-AUX B.11.11.08 Advanced Optimization Tools

June 2003 bundle is installed.
can I still apply these patches
are there patches on top of 11.11.08 ?

Re: signal 11 when linking c++ binary

Ermin Borovac — Wed, 06 Apr 2005 18:27:20 GMT

Patches for version B.11.11.08 are

PHSS_29484
PHSS_29485

I can't see any notes in these patches specific to your problem; install them anyway.

Also it's a good idea to install latest linker patch.

PHSS_30970

Re: signal 11 when linking c++ binary

A. Clay Stephenson — Wed, 06 Apr 2005 19:03:06 GMT

By all means apply any compiler/linker patches. If the problem persists, I would try compiling by turning off all optimization. I've occasionally seen the optimizer produce unstable code.

This is one of those problems that should be reported to HP.

Re: signal 11 when linking c++ binary

Nagarajan Ragunathan — Mon, 11 Apr 2005 16:37:12 GMT

I could link it by turning off the optimization. Thanks.

But when executing it, getting the following error:
aCC runtime: Error 22 from shl_findsym(/usr/lib/libCsup_v2.2,_shlInit)
Abort(coredump)

Re: signal 11 when linking c++ binary

A. Clay Stephenson — Mon, 11 Apr 2005 17:31:35 GMT

I doubt this has anything to do with your linker problems. It's now time to compile everything with the -g flag, don't strip the code; execute it and let it dump core. You then use gdb to examine a stack trace.

Re: signal 11 when linking c++ binary

A. Clay Stephenson — Mon, 11 Apr 2005 17:44:28 GMT

It's also a good idea to do a man shl_findsym and see what conditions can set errno = EINVAL (22). This is debugging 101.

Re: signal 11 when linking c++ binary

Nagarajan Ragunathan — Mon, 11 Apr 2005 18:13:59 GMT

I already did the debugging to figure what is happening here.
gdb stack shows
#0 0xc020a110 in kill+0x10 () from /usr/lib/libc.2
#1 0xc01a500c in raise+0x24 () from /usr/lib/libc.2
#2 0xc01e53f0 in abort_C+0x160 () from /usr/lib/libc.2
#3 0xc01e544c in abort+0x1c () from /usr/lib/libc.2
#4 0xc16e5154 in __shlinit+0x1e0 () from /usr/lib/libCsup_v2.2
#5 0xc16e7584 in _main+0x194 () from /usr/lib/libCsup_v2.2

I have tried -g, -AA options.
I have set SHLIB_PATH and LD_LIBRARY_PATH correctly. /usr/lib/libCsup_v2.2 did not have world read permissions and I have set it also( this is another problem)