linking on HP-UX 11.22 itanium is coming out with out of memory error

[Satya_6]

Hi,

I have an application which is built linking almost 250 static libraries (related to my application) and the following standard libraries.

-lGLU -lGL -lMrm -lXm -lXt -lXext -lXmu -lX11 -lm -lpthread -ljava

The linking on a HP-UX 11.22 itanium m/c is coming out saying

Out of Memory.
*** Error exit code 12

sometimes "/usr/ccs/bin/ld" comes out with signal 11 (Segmentation fault) with the following stack trace

#0 0x60000000c01671f0:1 in .stub+0x1111 () from /usr/lib/hpux32/libc.so.1
#1 0x60000000c0167060:0 in .stub+0xf80 () from /usr/lib/hpux32/libc.so.1
#2 0x60000000c0162f20:0 in .stub+0x9a0 () from /usr/lib/hpux32/libc.so.1
#3 0x60000000c016ee40:0 in malloc+0xa0 () from /usr/lib/hpux32/libc.so.1
#4 0x443700:0 in operator new[]+0x70 ()
#5 0x14f920:0 in Archive_library::process_member_list+0x350 ()
#6 0x1543a0:0 in Linker_driver::library_exists+0x4d0 ()
#7 0x14a6d0:0 in Linker_driver::find_library+0xf0 ()
#8 0x149720:0 in Linker_driver::set_library+0x1e0 ()
#9 0x1e4150:0 in Linker_driver::process_args+0x14f0 ()
#10 0x1f05c0:0 in Linker_driver::go+0xd0 ()
#11 0x213b50:0 in main+0x270 ()

Following are the memory details

Physical memory : 2042 MB
Swap : 4096 MB
maxdsiz : 3 GB
maxtsize and maxssiz = 1GB
dbc_max_pct and dbc_min_pct = 20

If I check the memory activity during linking, I don't see anything strange.

Please suggest a way out

TIA
satya

[Paula J Frazer-Campbell]

Hi

What is your dbc Max and Min settings


I would suggest Max = 10 and min 2.


Paula

[Paula J Frazer-Campbell]

IGNORE my last setting


That should be MAX 20 and Min 4


Sorry

Paula

[Satya_6]

Hi,

The dbc_max_pct is already set to 20, and even the min value is set to 20, and does the min value matter much to this problem?

TIA
satya

[Mike Stroyan]

PHSS_28971 includes a 64-bit version of the linker. With that linker the only barriers to it mallocing as much memory as it wants are ulimit, maxdsiz_64bit, and available swap space.

If a link still fails with that patch, you could use the tusc system call trace tool to see just how big the process is getting before it fails.