fdo-mirrors/dbus
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/dbus/dbus.git synced 2026-05-05 08:48:07 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

dbus_shutdown: document its effect on shared connections

Browse source 
In practice, the sort of applications that call dbus_shutdown()
(e.g. regression tests) will want to either use private connections,
or turn off exit-on-disconnect on the shared connection, or both.

Bug: https://bugs.freedesktop.org/show_bug.cgi?id=16924
This commit is contained in:
Simon McVittie 2014-09-10 16:20:52 +01:00
parent eca46a2341
commit c88525f815
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
dbus/dbus-memory.c
View file

@ -862,6 +862,13 @@ _dbus_register_shutdown_func_unlocked (DBusShutdownFunction func,
* You MUST free all memory and release all reference counts
* returned to you by libdbus prior to calling dbus_shutdown().
*
* If a shared connection is open, calling dbus_shutdown() will
* drain its queue of messages and disconnect it. In particular,
* this will result in processing of the special Disconnected
* signal, which may result in a call to _exit(), unless you
* have used dbus_connection_set_exit_on_disconnect() to disable
* that behaviour.
*
* You can't continue to use any D-Bus objects, such as connections,
* that were allocated prior to dbus_shutdown(). You can, however,
* start over; call dbus_threads_init() again, create new connections,