Calling back to a calling process after dbus_g_proxy_call_no_reply

[Havoc Pennington]

Hi,

On Thu, Aug 14, 2008 at 12:04 AM, Braden McDaniel <braden at endoframe.com> wrote:
> So it would seem.
>
> When I look at the host process in gdb, it's camped out in __poll
> (called from g_main_context_iterate). Any suggestions for debugging
> this?
>

That just means it's waiting in the main loop for something to happen,
afaik. So maybe the problem is nothing is happening. Or whatever is
happening isn't connected to the main loop as it should be.

Havoc