Runtime error- 26418 Bus error(coredump)

[Kalicharan]

Hi,
I dont find any issue in code, it is executing all the instructions properly, but when exiting, it gives the coredump.

Details-

(gdb) bt
#0 0x60000000deeb8c60:1 in signal_handler_catch () at opsig.c:424
#1
#2 0x60000000deeb8c60:1 in signal_handler_catch () at opsig.c:424
#3
#4 0x10dfc40:0 in __rw::__string_ref,std::allocator >::__references (this=0xfffffffe)
at /opt/aCC/include_std/rw/string_ref:237
#5 0x10e1760:0 in std::basic_string,std::allocator >::_C_unlink (this=0x8e8892c) at /opt/aCC/include_std/string:995
#6 0x10dc320:0 in std::basic_string,std::allocator >::~basic_string()+0x60 ()
#7 0x60000000c0888140:0 in __cxa_finalize+0x1e0 ()
from /usr/lib/hpux32/libCsup.so.1
#8 0x60000000c0887f10:0 in __cxxTerm_body()+0x30 ()
from /usr/lib/hpux32/libCsup.so.1
#9 0x60000000c0887dc0:0 in __cxxTerm+0x20 () from /usr/lib/hpux32/libCsup.so.1
#10 0x60000000c02a4700:0 in __exit_handler+0xa0 ()
from /usr/lib/hpux32/libc.so.1
Current language: auto; currently c

[Kalicharan]

More Information-
(gdb) disas $pc-16*4 $pc+16
Dump of assembler code from 0x60000000deeb8c20:0 to 0x60000000deeb8c70:0:
;;; DOC Line Information: [Line, Column Start, Column End] [Line, Column] [Line]
;;; File: opsig.c
;;; Line: 387
0x60000000deeb8c20:0 :
ld4.s r14=[r34]
0x60000000deeb8c20:1 :
addp4 r9=60,r33
0x60000000deeb8c20:2 :
cmp4.ne.unc p6=r0,r33;;
0x60000000deeb8c30:0 :
ld4.s r11=[r9]
0x60000000deeb8c30:1 :
(p6) chk.s.i r14,signal_handler_catch+0x400
0x60000000deeb8c30:2 :
(p6) cmp4.lt.unc p6=r0,r14;;
0x60000000deeb8c40:0 :
(p6) st2 [r39]=r42
0x60000000deeb8c40:1 :
(p6) chk.s.m r11,signal_handler_catch+0x420
0x60000000deeb8c40:2 :
nop.i 0x0
---Type to continue, or q to quit---
0x60000000deeb8c50:0 :
(p6) st4 [r10]=r11
;;; Line: 424
0x60000000deeb8c50:1 :
nop.m 0x0
0x60000000deeb8c50:2 :
br.many signal_handler_catch+0x140;;
0x60000000deeb8c60:0 :
adds r15=-48,r9;;
0x60000000deeb8c60:1 :
ld4 r14=[r15]
0x60000000deeb8c60:2 :
nop.i 0x0;;
End of assembler dump.


(gdb) info reg
pr0: 0x1
pr1: 0x1
pr2: 0x1
pr3: 0
pr4: 0
pr5: 0
pr6: 0x1
pr7: 0
pr8: 0
pr9: 0
pr10: 0
pr11: 0x1
pr12: 0
pr13: 0
pr14: 0x1
pr15: 0x1
pr16: 0
pr17: 0
pr18: 0
pr19: 0
pr20: 0
pr21: 0
pr22: 0
---Type to continue, or q to quit---
pr23: 0
pr24: 0
pr25: 0
pr26: 0
pr27: 0
pr28: 0
pr29: 0
pr30: 0
pr31: 0
pr32: 0
pr33: 0
pr34: 0
pr35: 0
pr36: 0
pr37: 0
pr38: 0
pr39: 0
pr40: 0
pr41: 0
pr42: 0
pr43: 0
pr44: 0
pr45: 0
---Type to continue, or q to quit---
pr46: 0
pr47: 0
pr48: 0
pr49: 0
pr50: 0
pr51: 0
pr52: 0
pr53: 0
pr54: 0
pr55: 0
pr56: 0
pr57: 0
pr58: 0
pr59: 0
pr60: 0
pr61: 0
pr62: 0
pr63: 0
gr0: 0
gr1: 0x2000000067746738
gr2: 0x60000000c0887f10
gr3: 0
gr4: 0
---Type to continue, or q to quit---
gr5: 0xc000000000000408
gr6: 0x60000000c004b4e0
gr7: 0x20000000678f97e0
gr8: 0x200000007ffe8ff0
gr9: 0x3d
gr10: 0x200000007ffe9000
gr11: NaT
gr12: 0x200000007ffe8fd0
gr13: 0x2000000067437080
gr14: NaT
gr15: 0xd
gr16: 0
gr17: 0
gr18: 0x200000007ffe9004
gr19: 0xec1af64
gr20: 0xec1af68
gr21: 0x20000000674370f4
gr22: 0
gr23: 0x2
gr24: 0x200000007ffe9008
gr25: 0x200000007ffe9000
gr26: 0x200000007ffe9004
gr27: 0x200000007fff32c0
---Type to continue, or q to quit---
gr28: 0x8
gr29: 0
gr30: 0
gr31: 0x200000007ffe8ff1
gr32: 0xa
gr33: 0x1
gr34: 0xd
gr35: 0x2000000067746738
gr36: 0xc000000000000085
gr37: 0xe0000001800028e0
gr38: 0xc847
gr39: 0x200000007ffe8ff2
gr40: 0x17ffe9200
gr41: 0x67742ac0
gr42: 0x1
gr43: 0x2000000067738b70
gr44: 0x200000006773b30d
gr45: 0x200000007ffe8ff0
gr46: 0x2000000067738b70
gr47: 0x200000007ffe8ff0
gr48: 0
gr49: 0x14
gr50: 0x53
---Type to continue, or q to quit---
gr51: 0x1
gr52: 0x710
br0: 0x60000000deeb8b70
br1: 0
br2: 0
br3: 0
br4: 0
br5: 0
br6: 0x60000000c023d080
br7: 0x60000000c01d7340
rsc: 0x1f
bsp: 0x20000000678ff510
bspst: 0x20000000678ff508
rnat: 0
ccv: 0
unat: 0
fpsr: 0x9804c0270033f
pfs: 0xc000000000000795
(sor:0, sol:15, sof:21)
lc: 0
ec: 0
ip: 0x60000000deeb8c60:1
cfm: 0x795

(sor:0, sol:15, sof:21)
psr: 0

[Dennis Handly]

>when exiting, it gives the coredump.

This is destroying a global string. Either it has been corrupted or being destroyed twice.
It would be useful to know what $r32 was in frame 6. Also do: x /4x $r32

>More Information
0x60000000deeb8c20:0 signal_handler_catch

This is useless, you need to look at frame 4, where it is getting the first signal.
And the signal handler is broken because it gets another signal.

[Kalicharan]

Thanks for your help.
Problem was solved by clearing the global string.

Thnaks.

[Dennis Handly]

>Problem was solved by clearing the global string.

That probably pushes the problem elsewhere??

[Dennis Handly]

>Problem was solved by clearing the global string.

That probably pushes the problem elsewhere.
I.e. if you have defined a global string in the executable AND a shlib, you will get this.

Because empty strings are handled special and never destroyed, that's probably why it now works.

[Kalicharan]

So what will be the final solution?
As it was showing problem in string, now what options do I have to get rid of the string?

[Dennis Handly]

>So what will be the final solution? Now what options do I have to get rid of the string?

You have to figure out what is the name of the string and why it is defined in multiple load modules. Or why it was corrupted.

In frame 6, what is the value of $r32:
p /x $r32
x /x $r32

From frame 5, it should be 0x8e8892c.
Try: info mod $r32