Need some more help, sorry for the trouble...<br><br>I am able to send and recv fsignals fine, but i see that signals get dropped rarely...is that even possible?<br><br>To send the signal i do the following steps in my app
<br><br>dbus_bus_get()<br>dbus_message_new_signal()<br>dbus_message_append_args()<br>dbus_connection_send()<br>dbus_connection_flush()<br>dbus_message_unref()<br>dbus_connection_unref()<br>exits program.<br><br>One the recv side i add a match rule and set a filter function.
<br><br>If i run the send app manually a few times from cmd line, i rarely see in the recv terminal that the signal has not been got (i use fprintfs).<br>It happens once in 30 or 40 tries i do. Randomly. <br><br>I have error checks and debug print statements for each of the calls so i know none of calls themselves fail. Send app exits as a sucess but the recv side never got the signal sent.
<br><br>Are there any tips for debugging this kind of problem. Or am i missing something here.<br><br>Thanks!<br>-Krish<br><br><div><span class="gmail_quote">On 1/24/07, <b class="gmail_sendername">John (J5) Palmieri</b> <
<a href="mailto:johnp@redhat.com">johnp@redhat.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Wed, 2007-01-24 at 16:27 -0500, Havoc Pennington wrote:
<br><br>><br>> > 1. Is this a correct way to recv signals? Do i have to do<br>> > dbus_message_unref(message) in the filter function after handling it<br>> > before i return?<br>><br>> I don't believe so, I could misremember, but it would be documented if
<br>> you did have to probably.<br><br>Hmm, wait. I might be misremembering too. The filter function may<br>unref for you and I think I was thinking of needing to unref after<br>creating a reply message. So if one needs to keep a message around they
<br>need to ref it.<br><br>--<br>John (J5) Palmieri <<a href="mailto:johnp@redhat.com">johnp@redhat.com</a>><br><br></blockquote></div><br>