Re: hang in gconfd

[Havoc Pennington <hp redhat com>]

jacob berkman <jacob@ximian.com> writes:
> i'm running GConf-1.0.7-2, and my gconfd hung (which causes all
> gconf-using programs to hang.  since gnome 2 apps call gconf at startup,
> no gnome 2 apps would run).
> 
> here's the stack trace at the time of the hang.
> 

FWIW this has been happening (rarely) for a long time, even in gconf 1
with ORBit 1. It is unreproduceable as far as I can tell. I asked for
assistance with it on orbit-list once before, I think, as I have no
idea what would cause an ORBit outgoing oneway call to stick like
this.

If oneway calls can hang, then we have a big problem, because I have
no idea how to make a server robust if any client can hang it.  Or if
they only hang in avoidable circumstances, I'd like to know what those
are.
 
> (no debugging symbols found)...(no debugging symbols found)...0x4021f0e7 in __writev (fd=9, vector=0x805b7c8, count=9) at ../sysdeps/unix/sysv/linux/writev.c:51
> 	in ../sysdeps/unix/sysv/linux/writev.c
> #0  0x4021f0e7 in __writev (fd=9, vector=0x805b7c8, count=9) at ../sysdeps/unix/sysv/linux/writev.c:51
> #1  0x400d1326 in giop_send_buffer_write (send_buffer=0x8059e50) at giop-msg-buffer.c:230
> #2  0x4005837b in ConfigListener_ping () from /usr/lib/libgconf-1.so.1
> #3  0x0804c4ff in gconf_database_free ()

This is gconfd pinging a client program, the ping is:

interface ConfigListener {

   ...

   oneway void ping ();

My understanding is that is not supposed to block.

Havoc