Nevermind, i have figured out what the output from dbus-monitor means in the previous email. It doesnt offer much clue on why my connection is closed down though. Will keep looking. Thanks! -Prakash <div> On 4/12/07, Krishna R <<a href="mailto:sith.list@gmail.com">sith.list@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I have attached the output for dbus-monitor. crash.txt is when my process exits because the daemon closes the connection, the nocrash.txt is when things work as normal. I dont know enuff about dbus specs to infer anything looking at the files itself, can anyone help pls. If i add DBUS_VERBOSE=1 when i start the daemon, it does not close the connection (dbus_nocrash.txt), if i dont then it happens everytime (dbus_crash.txt)! Any help is appreciated. Thanks.<div> <div>On 4/12/07, Krishna R <<a href="mailto:sith.list@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">sith.list@gmail.com</a> > wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Thiago, Thanks for the reply, coupla dumb q. 1. Process A sends a signal to an interface X which is routed thru dbus daemon and process B recvs it in that interface X, if dbus-daemon closes socket with B, it means that B has sent an invalid message to the daemon correct? Or does it happen if A sends an invalid message to the interface X? I am asking this because B does nothing more than recving the message and setting the result as handled. 2. Since DBUS_VERBOSE etc seems to change the timing, i may have add prints in the code where the daemon detects invalid signal and closes the connection. Can you pls tell me where i should look for this part of the code? searching for connection_close or disconnect or invalid message, hits too many files. If you dont know from the top of your head, its ok, i will figure it out. Thanks!<div> <div>On 4/11/07, Thiago Macieira <<a href="mailto:thiago@kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> thiago@kde.org</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Krishna R wrote: >Further probing lead to disconnect signal being the cause of > do_io_error() in dbus-transport-socket.c, it was called because > do_reading() which reads from the socket and gets bytes_read = 0. That > means the socket was closed on the other end? Yes. >The question i have is why is the dbus-daemon closing the socket? Or is > it? It is and it does so because it received an invalid message. If you strace the daemon or if you run it in debug mode, it should say why it did that. >dbus-daemon, A and B are started one after another at boot in the >foreground. Is there some problem where the session bus is not fully >initialized? That may not be because atleast one signal from A reaches > B. I don't think so. -- Thiago Macieira - thiago (AT) <a href="http://macieira.info" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> macieira.info</a> - thiago (AT) <a href="http://kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">kde.org</a>   PGP/GPG: 0x6EF45358; fingerprint:   E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 </blockquote> </div> </div></blockquote></div> </div> </blockquote></div>