AIX

Hello,

One of our customer is getting segmentation fault when he runs his shell script which invokes our executable on AIX 6.1.

On AIX 5.3, there were no issues.

Here is the truss output.

Code:

811242: __loadx(0x0A040000, 0xF0D3A26C, 0x00000000, 0x00000009, 0x00000000) = 0xF026E884
811242: loadbind(0, 0xF0D86E54, 0xF027E304)		= 0
811242:     Received signal #11, SIGSEGV [default]
811242: *** process killed ***

Here is the stack trace

Code:

# gdb -c core
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "powerpc-ibm-aix5.1.0.0".
Core was generated by `bteq'.
Program terminated with signal 11, Segmentation fault.

warning: Could not open `bteq' as an executable file: A file or directory in the
 path name does not exist.
#0  0xd10affbc in _Grow__Q2_3std12basic_stringXTcTQ2_3std11char_traitsXTc_TQ2_3std9allocatorXTc () from /usr/lib/libC.a(ansi_32.o)
(gdb) bt
#0  0xd10affbc in _Grow__Q2_3std12basic_stringXTcTQ2_3std11char_traitsXTc_TQ2_3s
td9allocatorXTc () from /usr/lib/libC.a(ansi_32.o)
Segmentation fault(coredump)
#

It is showing unresolved symbol.

what is this symbol "_Grow__Q2_3std12basic_stringXTcTQ2_3std11char_traitsXTc_TQ2_3std9allocatorXTc ()" about?

From which version of libC.a , above symbol can be available?

we have sugessted to use LDR_CNTRL variable as
getting segfault and got signal 11 in this case.

""In case of AIX operating system, for 32-bit executables, SIGSEGV can be generated due to insufficient segment-size.
The way the memory model of AIX is designed, segments, by default, have a fixed size (256Mb).
Incase if a process requests more memory than this, a segment violation occurs and the operating system delivers a SIGSEGV signal to the process.
For resolving this, you can link with -bmaxdata=<num> or set the runtime environmen variable LDR_CNTRL=MAXDATA."""

With LDR_CNTRL set, one of the shell script of customer was sucessful.

I am maily concern with the symbol shown in stack trace.
what could be the cause for that either invalid version of libC.a OR anything else?


Thanks

regards,
Srikrishna Erra.

Moderator's Comments:

Please use the CODE-tags i edited into your post yourself from now on when quoting code, code-fragments or terminal output. Thank you.