cancel
Showing results for 
Search instead for 
Did you mean: 

trashed stack libdcekt.1

SOLVED
Go to solution
moory
Occasional Visitor

trashed stack libdcekt.1

hi

have a process that monitors the status of dce application servers. Today it has started (worked fine last week) failing with a 'Pid xxxxx killed due to trashed stack' message

If I take the core file and run it throught gdb I get...
> gdb director.exe core
HP gdb 5.2 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00
and target hppa1.1-hp-hpux11.00.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.2 (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 `director.exe'.
Program terminated with signal 4, Illegal instruction.
Unknown si_code. Report to HP.
#0 0xc4ddc334 in cdsCvtFullToOpq+0x4 () from /usr/lib/libdcekt.1
(gdb) bt
#0 0xc4ddc334 in cdsCvtFullToOpq+0x4 () from /usr/lib/libdcekt.1
#1 0xc4de3650 in cdsExpandStrFull+0x30 () from /usr/lib/libdcekt.1
#2 0xc4d3d9f8 in rpc__ns_expand_entry_name+0x30 () from /usr/lib/libdcekt.1
#3 0xc4d3d99c in rpc_ns_entry_expand_name+0x12c () from /usr/lib/libdcekt.1
#4 0xc4e22ca8 in rca_site_bind+0x1e0 () from /usr/lib/libdcekt.1
#5 0xc4ea3de8 in sec__id_parse_name+0x930 () from /usr/lib/libdcekt.1
#6 0xc4ea4598 in sec_id_global_parse_name+0x50 () from /usr/lib/libdcekt.1
#7 0xc4e661ac in sec_krb_sec_parse_name+0xec () from /usr/lib/libdcekt.1
#8 0xc4d353bc in rpc__krb_bnd_set_auth+0x30c () from /usr/lib/libdcekt.1
#9 0xc4ccec40 in rpc_binding_set_auth_info+0x228 () from /usr/lib/libdcekt.1
#10 0x3052c in GetArrivalsHandle (ifSpec=0x4000c360,
princName=0x6fb10bf0 "/.:/unibill_o/server/SMS_PRD_AUDSMEM", netAddr=0x0,
protseq=0x400077f0 "ncadg_ip_udp") at getArrivalsHandle.c:336
#11 0x6b1e4 in registerCallbackAndBind (thisObj=0x40245fc8) at query_Monitor.c:1905
#12 0x67e78 in query_object (thisObj=0x40245fc8, callingFunc=0x4000b850 "statusJobProcess")
at query_Monitor.c:1730
#13 0xac4f8 in statusJobProcess (thisJob=0x4024a540, thisThreadId=18)
at statusJobPool.c:270
#14 0xaabd0 in statusJobProcessList (data=0x40232e20) at statusJobPool.c:223
#15 0xc005b00c in __pthread_body+0x44 () from /usr/lib/libpthread.1
#16 0xc00652b4 in __pthread_start+0x14 () from /usr/lib/libpthread.1
(gdb)

any help would be appreciated

thanks
2 REPLIES
Dennis Handly
Acclaimed Contributor
Solution

Re: trashed stack libdcekt.1

>Pid xxxxx killed due to trashed stack' message

This typically occurs if the SP register isn't valid.
You could also have a thread stack overflow.
What is the size of your thread stack? See my comments in this thread. You need to check frame 0 and frame 16 in this case.
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1102425
moory
Occasional Visitor

Re: trashed stack libdcekt.1

Dennis - you are a star

thankyou very much