Help in analysis tusc output

[Jai Gopal]

Hi Admin

One of our application is creating core dump mentioned as SIGBUS error.I had taken tusc output thourgh PID.But not able to makeout anything thing.Need help to know that do we need to change some parameter on OS side or it is really application problem so that it can take up with application team.

It is telecom billing application running on 32 way superdome with os as hpux11iv1.

Find attached the tusc output.

Thanks in advance.

Jai

[Steven E. Protter]

Shalom Jai,

The application has an error concerning memory. It might involved shared memory.

Most likely you need to kick this problem back to the developers and ask them to look into how they are using memory.

It is possible you don't have enough shared memory allocated, however this looks like you need to see application code to be more specific.

Try and tell the developers exactly what you were doing when the fault occurred.

SEP

[A. Clay Stephenson]

Rather than tusc output, you really need a stack trace but to really nail this down, you should have your developers compile with the -g flag (this includes debugger data in the object files) and then allow the program to crash. Using a symbolic debugger such as gdb, you can then perform a stack trace and it should take you to the exact offending source code line.

[Jai Gopal]

Hi clay and steve,

Thanks for your input,we had run gdb on same.The output come out with as unknown bus error.The error is mentioned below

The gdb(debugger program) on this core file on one of our test systems and did a backtrace and it gave me the following information.

Detected 64-bit corefile.

Invoking /opt/langtools/bin/gdb64.

HP gdb 5.5.0 for PA-RISC 2.0 (wide), HP-UX 11.00

and target hppa2.0w-hp-hpux11.00.

Copyright 1986 - 2001 Free Software Foundation, Inc.

Hewlett-Packard Wildebeest 5.5.0 (based on GDB) is covered by the

GNU General Public License. Type "show copying" to see the conditions to

change it and/or distribute copies. Type "show warranty" for warranty/support.
warning: Unknown symbols for 'core'; use the 'symbol-file' command.
Core was generated by `bch'.
Program terminated with signal 10, Bus error.
BUS_UNKNOWN - Unknown Error
#0 0x40000000005b3df4 in ()
Cannot access memory at address 0x40000000005b3df4.
(gdb) symbol-file /ud00/work/bin/bch
Reading symbols from /ud00/work/bin/bch...warning: Load module /ud00/work/bin/bch has been stripped.
Debugging information is not available.
(no debugging symbols found)...done.
(gdb) bt
#0 0x40000000005b3df4 in + 0x800001f ()
#1 0x40000000005aaa28 in + 0x800001f ()
#2 0x4000000000608f48 in + 0x800001f ()
#3 0x40000000006064b8 in + 0x800001f ()
#4 0x400000000052a434 in + 0x800001f ()

Error accessing memory address 0x0: Invalid argument.

(gdb) quit

So we can confirm to application team that it is related to appl. problem,need ur input.

Thanks in Advance.

Jai

[A. Clay Stephenson]

Tell the developers to alter the makefile and remove the strip command. That remove critical data that the debugger need.