Creating local method call+reply pair, causes assertion failures

[Havoc Pennington]

On Mon, 2005-11-28 at 10:12 +0000, Daniel P. Berrange wrote:
> I've puzzled over this problem for a while now & can't find a decent
> solution yet. The only way I can trigger the code to set the message
> serial, is to actually send the message over the connection, but as
> noted earlier, the whole point of this exercise is to avoid creating
> a real connection. I really don't want to have to create a abstract 
> layer around the dbus_message object, just to avoid this assertion 
> check, but I'm running out of options. Has anyone got any thoughts ?

There's a "debug pipe" connection in dbus-server-debug-pipe.c that dbus
itself uses for its unit tests. This is a little tricky to use though
(without threads) because you have to be sure you never accidentally
block on the connection waiting for yourself to reply ;-)

We could make set_serial public probably, not a big deal.

Havoc