Re: BonoboActivation locking up?



Hi Iain,

On Wed, 2002-01-09 at 03:12, iain wrote:
> I upgraded linc, but it still occurs.

	Ah - well looking at the trace:

> And a backtrace from the stalled bonobo-activation-server
> #0  0x40300bf4 in poll () from /lib/libc.so.6
> #1  0x40100ce0 in g_main_context_poll (context=0x8061320, timeout=-1, 
>     priority=2147483647, fds=0x80703b8, n_fds=4) at gmain.c:2547
> #2  0x4010027e in g_main_context_iterate (context=0x8061320, block=1, 
>     dispatch=1, self=0x80bcec0) at gmain.c:2224
> #3  0x401009a0 in g_main_loop_run (loop=0x80733c0) at gmain.c:2449
> #4  0x400230af in bonobo_activation_internal_server_by_forking_extended (
>     cmd=0xbfffe1f0, set_process_group=1, fd_arg=2, display=0x807c048 ":0", 
>     od_iorstr=0x80713b9 "IOR:010335401f00000049444c3a426f6e6f626f2f4f626a6563744469726563746f72793a312e300030030000000054424f640000000101020005000000554e4958004e495821000000646973636f6d616368696e6567756e2e70726574747970656f70"..., 
>     ev=0xbffff440) at bonobo-activation-fork-server.c:234
> #5  0x0805250f in od_server_activate_exe (si=0x80a3f94, actinfo=0xbfffe2d0, 
>     od_obj=0x80619a0, ev=0xbffff440) at object-directory-activate.c:175
...

	It seems that the real issue is getting the process to register it's
objects correctly. Can you export BONOBO_ACTIVATION_DEBUG_OUTPUT=1,
then bonobo-slay, then run your app; there was some timeout debug or
somesuch that ensured that the process returned an IOR in a certain
time but ..

	Somehow the IOR isn't getting back to bonobo-activation of the
component you're trying to register. I'd also recommend checking to
see if the component is already registerd and exiting the app if it's not.

	Regards,

		Michael.


-- 
 mmeeks gnu org  <><, Pseudo Engineer, itinerant idiot




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]