Menu
▾
▴
[Sblim-issues] [ sblim-Bugs-3087587 ] sfcb Segmentation fault in createInstance
|
From: SourceForge.net <no...@so...> - 2010-10-29 16:07:55
|
Bugs item #3087587, was opened at 2010-10-14 13:18 Message generated for change (Comment added) made by tjwarne You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=712784&aid=3087587&group_id=128809 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: sfcb Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tom Warne (tjwarne) Assigned to: Chris Buccella (buccella) Summary: sfcb Segmentation fault in createInstance Initial Comment: Backtrace from core file: GNU gdb 6.4 Copyright 2005 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 "--host=i686-pc-linux-gnu --target=ppc-linux". Core was generated by `/usr/sbin/sfcbd -d'. Program terminated with signal 11, Segmentation fault. #0 0x0ff43d40 in createInstance (hdr=0x1005a530, info=0x1001e190, requestor=-48) at providerDrv.c:1567 1567 rci = info->instanceMI->ft->createInstance(info->instanceMI, ctx, result, (gdb) bt **NOTE: debug frames are hidden in bt display** #0 0x0ff43d40 in createInstance (hdr=0x1005a530, info=0x1001e190, requestor=-48) at providerDrv.c:1567 #1 0x0ff4bf5c in processProviderInvocationRequestsThread (prms=0x1001f118) at providerDrv.c:2719 #2 0x0fda3aec in start_thread (arg=<value optimized out>) at pthread_create.c:308 #3 0x0fcf28fc in clone () from /opt/mcp/ppcnf/crossroot/lib/libc.so.6 ---------------------------------------------------------------------- >Comment By: Tom Warne (tjwarne) Date: 2010-10-29 11:07 Message: Yes, the backtrace matches the trace output. Here is more detail on the null pointer that caused the segmentation fault: Core was generated by `/usr/sbin/sfcbd -d'. Program terminated with signal 11, Segmentation fault. #0 0x0ff43d40 in createInstance (hdr=0x1005a530, info=0x1001e190, requestor=-48) at providerDrv.c:1567 1567 rci = info->instanceMI->ft->createInstance(info->instanceMI, ctx, result, (gdb) print info $1 = (ProviderInfo *) 0x1001e190 (gdb) print info->instanceMI $2 = (CMPIInstanceMI *) 0x0 ---------------------------------------------------------------------- Comment By: Chris Buccella (buccella) Date: 2010-10-22 19:52 Message: Does the backtrace in the bug summary match the trace output in your 10/14 comment? I ask because the backtrace if in a createInstance, and the SEGV is in ClassProvider, which isn't registered as an instance provider. ---------------------------------------------------------------------- Comment By: Tom Warne (tjwarne) Date: 2010-10-14 18:23 Message: I forgot to mention that this is sfcb 1.3.8. I looked at our trace file and discovered that some old indication subscriptions were hanging around, so this is and added factor. sfcbd was started up at around 00000220. After indications were enabled, sfcbd started querying my provider for CIM_RegisteredProfile instances and associations: 00000224.917631| 2225|CIMP | 159|>> [cimpauth.C, _sfcGetSlpHostname] 00000224.922473| 2225|CIMP | 133|I> [cimpSendRecvAuthMessage] Packed Reply Message: 00000224.922473| 2225|CIMP | 133|~[0x0000] 31302E30 2E302E32 343500 *10.0.0.245. * 00000224.924204| 2225|CIMP | 179|<< [cimpauth.C, _sfcGetSlpHostname] HostName: 10.0.0.245 00000225.342718| 2347|CIMP | 141|>> [CIMP_FipS_EnumInstances] 00000225.342800| 2347|CIMP | 108|>> [cimpSendRecvQueryMessage] ClassName: FipS_RegisteredProfile 00000225.401647| 2347|CIMP | 170|<< [CIMP_FipS_EnumInstances] l_status.rc = 0x0, count = 10 00000225.590402| 2400|CIMP | 609|>> [CIMP_FipS_AssociatorNames] 00000225.590635| 2400|CIMP | 614|>> [cimpProcessAssoc] i_type: 1, ReferenceObjectPath: root/interop:SFCB_RegisteredProfile.InstanceID="CIM:SFCB_PR" 00000225.590923| 2400|CIMP | 642|<< [CIMP_FipS_AssociatorNames] l_status.rc = 0x5 00000225.676071| 2417|CIMP | 554|>> [CIMP_FipS_Associators] 00000225.676202| 2417|CIMP | 614|>> [cimpProcessAssoc] i_type: 0, ReferenceObjectPath: root/interop:SFCB_RegisteredProfile.InstanceID="CIM:SFCB_PR" 00000225.676455| 2417|CIMP | 653|E> [cimpProcessAssoc] l_status.rc = 0x5 00000225.693705| 2429|CIMP | 609|>> [CIMP_FipS_AssociatorNames] 00000225.693832| 2429|CIMP | 614|>> [cimpProcessAssoc] i_type: 1, ReferenceObjectPath: root/interop:SFCB_RegisteredProfile.InstanceID="CIM:SFCB_IP" 00000225.694096| 2429|CIMP | 642|<< [CIMP_FipS_AssociatorNames] l_status.rc = 0x5 00000225.715926| 2443|CIMP | 554|>> [CIMP_FipS_Associators] 00000225.716065| 2443|CIMP | 614|>> [cimpProcessAssoc] i_type: 0, ReferenceObjectPath: root/interop:SFCB_RegisteredProfile.InstanceID="CIM:SFCB_IP" 00000225.716323| 2443|CIMP | 587|<< [CIMP_FipS_Associators] l_status.rc = 0x5 00000225.745930| 2456|CIMP | 609|>> [CIMP_FipS_AssociatorNames] 00000225.746061| 2456|CIMP | 614|>> [cimpProcessAssoc] i_type: 1, ReferenceObjectPath: root/interop:FipS_RegisteredProfile.InstanceID="Service Processor" This continues for the 10 profiles supported. Then, there is no further activity until my indication provider receives 2 indications to be delivered: 00000265.183932| 2205|CIMPSRV | 447|INF> handleFspStateChangedEvent: Sending 2 indications for eventId:143 00000265.188665| 2273|CIMP | 273|I> [cimpIndicationMonitorThread] Received an indication delivery message 00000265.667417| 2273|CIMP | 357|I> [cimpIndicationMonitorThread] CBDeliverIndication rc = 0x0 00000265.753666| 2273|CIMP | 357|I> [cimpIndicationMonitorThread] CBDeliverIndication rc = 0x0 00000265.753740| 2273|CIMP | 260|I> [cimpIndicationMonitorThread] Waiting for an indication delivery message sfcbd reliable indication delivery kicks in: 00000290.851364| 661|SYSLOG | 225|<27>Jul 7 13:31:14 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) 00000290.851849| 661|SYSLOG | 225|<27>Jul 7 13:31:14 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) 00000290.852273| 661|SYSLOG | 225|<27>Jul 7 13:31:14 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) 00000290.852686| 661|SYSLOG | 225|<27>Jul 7 13:31:14 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) 00000310.936237| 661|SYSLOG | 225|<27>Jul 7 13:31:34 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) 00000310.936662| 661|SYSLOG | 225|<27>Jul 7 13:31:34 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) 00000310.937078| 661|SYSLOG | 225|<27>Jul 7 13:31:34 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) 00000310.937491| 661|SYSLOG | 225|<27>Jul 7 13:31:34 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) 00000335.004373| 661|SYSLOG | 225|<27>Jul 7 13:31:58 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) 00000335.004473| 661|SYSLOG | 225|<27>Jul 7 13:31:58 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) 00000349.540220| 661|SYSLOG | 225|<27>Jul 7 13:32:13 sfcb[2213]: Problem processing indication to http://9.3.20.222:6989. sfcb rc: 4 CURL error: 7 (Failed to connect to host.) Just before the core dump, it looks like sfcbd is starting to repeat the CIM_RegisteredProfile queries: 00000511.362780| 2225|CIMP | 159|>> [cimpauth.C, _sfcGetSlpHostname] 00000511.364981| 2225|CIMP | 133|I> [cimpSendRecvAuthMessage] Packed Reply Message: 00000511.364981| 2225|CIMP | 133|~[0x0000] 31302E30 2E302E32 343500 *10.0.0.245. * 00000511.365132| 2225|CIMP | 179|<< [cimpauth.C, _sfcGetSlpHostname] HostName: 10.0.0.245 00000511.795005| 661|SYSLOG | 225|<27>Jul 7 13:34:55 sfcb[2213]: -#- ClassProvider - 2216 provider exiting due to a SIGSEGV signal ---------------------------------------------------------------------- Comment By: Chris Buccella (buccella) Date: 2010-10-14 16:40 Message: Can you post the XML that causes this? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=712784&aid=3087587&group_id=128809 |