Operating System - HP-UX
1753783 Members
6928 Online
108799 Solutions
New Discussion юеВ

Re: Generation of core in binary directory,Program terminated with signal 11

 
SOLVED
Go to solution
Mir1
Occasional Contributor

Generation of core in binary directory,Program terminated with signal 11

Generation of core in binary directory,Program terminated with signal 11
Hi all,

Please fnd the gdb trace of core file.

account:/TCS/crd/BACK/LOG/msghandle> gdb msghandle core
HP gdb 6.1 for HP Itanium (32 or 64 bit) and target HP-UX 11iv2 and 11iv3.
Copyright 1986 - 2009 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 6.1 (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.
..
Core was generated by `msghandle'.
Program terminated with signal 11, Segmentation fault.
SEGV_ACCERR - Invalid Permissions for object

warning: Load module /TCS/crd/src/modules/libcreq.so has been stripped.
Debugging information is not available.


warning: Load module /TCS/crd/src/modules/libtcscomm.so has been stripped.
Debugging information is not available.


warning: Load module /TCS/crd/src/modules/libtcsutil.so has been stripped.
Debugging information is not available.


warning: Load module /oracle/10g/lib/libclntsh.so.10.1 has been stripped.
Debugging information is not available.


warning: Load module /oracle/10g/lib/libnnz10.so has been stripped.
Debugging information is not available.

#0 0xc000000007fe6940:0 in nsdo+0x3bd0 ()
from /oracle/10g/lib/libclntsh.so.10.1
(gdb)
(gdb) f 0
#0 0xc000000007fe6940:0 in nsdo+0x3bd0 ()
from /oracle/10g/lib/libclntsh.so.10.1
(gdb) where
#0 0xc000000007fe6940:0 in nsdo+0x3bd0 ()
from /oracle/10g/lib/libclntsh.so.10.1
#1 0xc000000007fe2b30:0 in nsbrecv+0x90 ()
from /oracle/10g/lib/libclntsh.so.10.1
#2 0xc00000000805bbe0:0 in nioqrc+0x3c0 ()
from /oracle/10g/lib/libclntsh.so.10.1
#3 0xc00000000831bf00:0 in ttcdrv+0x910 ()
from /oracle/10g/lib/libclntsh.so.10.1
#4 0xc00000000806b0f0:0 in nioqwa+0xd0 ()
from /oracle/10g/lib/libclntsh.so.10.1
#5 0xc000000007cc95c0:0 in upirtrc+0xde0 ()
from /oracle/10g/lib/libclntsh.so.10.1
#6 0xc000000007ba8120:0 in kpurcsc+0x100 ()
from /oracle/10g/lib/libclntsh.so.10.1
#7 0xc000000007b25360:0 in kpuexecv8+0xb60 ()
from /oracle/10g/lib/libclntsh.so.10.1
#8 0xc000000007b28480:0 in kpuexec+0xab0 ()
from /oracle/10g/lib/libclntsh.so.10.1
#9 0xc000000007c4de70:0 in OCIStmtExecute+0x50 ()
from /oracle/10g/lib/libclntsh.so.10.1
#10 0xc000000007aa8f60:0 in sqlcucExecute+0x80 ()
from /oracle/10g/lib/libclntsh.so.10.1
#11 0xc000000007a92d30:0 in sqlall+0x23c0 ()
---Type <return> to continue, or q <return> to quit---
from /oracle/10g/lib/libclntsh.so.10.1
#12 0xc000000007a9da50:0 in sqlatm+0x310 ()
from /oracle/10g/lib/libclntsh.so.10.1
#13 0xc000000007a7d320:0 in sqlnst+0x4a00 ()
from /oracle/10g/lib/libclntsh.so.10.1
#14 0xc000000007a591d0:0 in sqlcxt+0x7d0 ()
from /oracle/10g/lib/libclntsh.so.10.1
#15 0x40000000000083b0:0 in inst_bl_msg_body () at recv_msg_handle.c:399
#16 0x4000000000008dd0:0 in load_BL_msg () at recv_msg_handle.c:571
#17 0x40000000000069b0:0 in packet_handler () at msg_head.c:179
#18 0xc0000000000cff40:0 in __pthread_bound_body+0x190 ()
from /usr/lib/hpux64/libpthread.so.1
(gdb)

By this gdb trace im not getting any hint,why its generating the core.
Please help.
2 REPLIES 2
Dennis Handly
Acclaimed Contributor
Solution

Re: Generation of core in binary directory,Program terminated with signal 11

> I'm not getting any hint, why it's generating the core.

 

Unless you have the Oracle source, you won't.  Especially with the unhelpful function names.

Most likely you hare passing in bad info to sqlcxt.

You could dump the assembly of the top frame:

(gdb) info reg

(gdb) disas $pc-16*20 $pc+16*20

Mir1
Occasional Contributor

Re: Generation of core in binary directory,Program terminated with signal 11

Thank you for your comment. The problem was solved by receiving a certain number of datas without using Thread, creating a file, and processing the DB later.