Missing dbus signals
kaustubh.ra at gmail.com
Wed Feb 25 23:24:34 PST 2009
I am using normal g_mail_loop for events integration in receiver side. And
the regular method of add_match & add_filter to poll on signals and read
them. I was too suspecting on the socket getting full but I added some
prints in - _dbus_connection_get_dispatch_status_unlocked . But can see
number "6" most of the time as number of incoming connections.
How can i avoid though if socket is getting full sometimes?
On Thu, Feb 26, 2009 at 11:44 AM, Thiago Macieira <thiago at kde.org> wrote:
> Kaustubh Atrawalkar wrote:
> >I can see these prints with
> >proper values of arguments being passed. So, as per logs i can see the
> > dbus signal message is being sent over the SYSTEM bus. But somehow its
> > being dropped at sometimes. The reporduciblity is 1 out of 10 thought..
> > Is there any suspect? How can i go for debugging it?
> My guess is that the socket got full and the DBusConnection toggle the
> Write DBusWatch, waiting for the possibility to write again.
> Does your code handle DBusWatch correctly? How does it do the event loop
> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
> PGP/GPG: 0x6EF45358; fingerprint:
> E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
> dbus mailing list
> dbus at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dbus