GDBusServer: Avoid handling incoming connections after stop() has been called
authorDavid Zeuthen <davidz@redhat.com>
Tue, 20 Jul 2010 16:14:30 +0000 (12:14 -0400)
committerDavid Zeuthen <davidz@redhat.com>
Tue, 20 Jul 2010 16:14:30 +0000 (12:14 -0400)
commitb3cf5cbd0bfcfe53f82a72d276683aebd15d3828
tree4dc83eb89bc82d5d6b7eb568b252dced94df616f
parent2be167f57c2b59d427aa54e2204bfaa906391b3e
GDBusServer: Avoid handling incoming connections after stop() has been called

Without this fix, we'd sometimes run code after stop() and finalize()
to handle incoming requests. This was observed in the gdbus-peer test
case occasionally crashing:

 $ ./gdbus-peer
 /gdbus/peer-to-peer: OK
 /gdbus/delayed-message-processing: OK
 /gdbus/nonce-tcp:
 GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GDBusServer'
 aborting...

Signed-off-by: David Zeuthen <davidz@redhat.com>
gio/gdbusserver.c