[Ekiga-devel-list] trouble with running ekiga head

[lin ma <lin ma oracle com>]

Hi,

Has anybody encountered a problem when Ekiga loading plugins. I got this 
on Debian 6.0.1/Ubuntu 10 and 11 with Ekiga header 
49d88d7d6918c493387743c1c1f2e070ede4b844, Opal-3.10.0 and Ptlib 2.10.0.

The stack trace is:

(gdb) run
Starting program: /usr/local/bin/ekiga
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffeb995700 (LWP 30852)]
[New Thread 0x7ffff7fad700 (LWP 30853)]
[New Thread 0x7ffff7f6c700 (LWP 30854)]
[New Thread 0x7ffff7f2b700 (LWP 30855)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff628679d in PPluginManager::GetPluginsDeviceNames 
(this=0x7ffff65e3440, serviceName=...,
    serviceType=..., userData=0) at ptlib/common/pluginmgr.cxx:326
326            PStringArray devices = ((PDevicePluginServiceDescriptor 
*)service.descriptor)->GetDeviceNames(userData);
(gdb) bt
#0  0x00007ffff628679d in PPluginManager::GetPluginsDeviceNames 
(this=0x7ffff65e3440, serviceName=...,
    serviceType=..., userData=0) at ptlib/common/pluginmgr.cxx:326
#1  0x00007ffff613a157 in PVideoInputDevice::GetDriversDeviceNames 
(driverName=..., pluginMgr=0x7ffff65e3440)
    at ptlib/common/videoio.cxx:1401
#2  0x00007ffff6c85cd7 in OpalManager::OpalManager (this=0x8be800)
    at /home/malin/ws/ekiga-all/opal-3.10.0/src/opal/manager.cxx:228
#3  0x00007ffff7779933 in Opal::CallManager::CallManager (this=0x8be760, 
_core=...)
    at ../lib/engine/components/opal/opal-call-manager.cpp:102
#4  0x00007ffff77a9b58 in OPALSpark::try_initialize_more (this=0x8b46d0, 
core=...)
    at ../lib/engine/components/opal/opal-main.cpp:116
#5  0x00007ffff76e09a8 in Ekiga::KickStart::kick (this=0x7fffffffe1a0, 
core=..., argc=0x7fffffffdffc,
    argv=0x7fffffffdff0) at ../lib/engine/framework/kickstart.cpp:134
#6  0x00007ffff76d12fa in engine_init (service_core=..., argc=1, 
argv=0x7fffffffe7a8)
    at ../lib/engine/engine.cpp:191
#7  0x0000000000449337 in main (argc=1, argv=0x7fffffffe7a8) at 
gui/main_window.cpp:4844
(gdb) p service
$1 = (const PPluginService &) @0x835020: {<PObject> = {_vptr.PObject = 
0x7ffff65bde50},
  serviceName = {<PCharArray> = {<PBaseArray<char>> = {<PAbstractArray> 
= {<PContainer> = {<PObject> = {
              _vptr.PObject = 0x7ffff65c4b70}, reference = 0x73f230}, 
elementSize = 1,
          theArray = 0x744cd8 "V4L2",
          allocatedDynamically = true}, <No data fields>}, <No data 
fields>}, <No data fields>},
  serviceType = {<PCharArray> = {<PBaseArray<char>> = {<PAbstractArray> 
= {<PContainer> = {<PObject> = {
              _vptr.PObject = 0x7ffff65c4b70}, reference = 0x73f210}, 
elementSize = 1,
          theArray = 0x71f6c8 "PVideoInputDevice",
          allocatedDynamically = true}, <No data fields>}, <No data 
fields>}, <No data fields>},
  descriptor = 0x7fffe2c17990}
(gdb) p *(PDevicePluginServiceDescriptor *)service.descriptor
$2 = {<PPluginServiceDescriptor> = {_vptr.PPluginServiceDescriptor = 
0x0, version = 0},
  static SeparatorChar = 9 '\t'}

This looks PPluginServiceDescriptor objects are deleted after the 
related plugins are registered. But I don't know when and why they are 
deleted. Does anybody have comments for that?

Thanks,
lin