| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
cb->disc_func or cb->conn_func could remove the callback so this needs
to be checked for before continuing processing.
|
|
This patch was generated by the following semantic patch
(http://coccinelle.lip6.fr/)
// <smpl>
@fix disable is_null,isnt_null1@
expression *E;
@@
- !E
+ E == NULL
// </smpl>
|
|
Pending call should be removed if the watch is removed since the
application no longer expect that to be reached and may already freed the
data associated with it.
|
|
The bus name should be resolved when adding a watch by service name since
messages do always come with sender set to owner's bus name, also it
should listen to owner updates since it can change without invalidating
the watch.
|
|
Services can be owned again so it is perfectly fine to keep the watch.
|
|
Avoid the memory leak of server_data.
|
|
This was triggering an assert inside libdbus when the timeout inside
the leaking pending call expired. The assert said that we were trying
to remove an nonexistent timeout.
|
|
filter_data_find return the first data registered in this case so there is
no guarantee that it return the same data as passed to
filter_data_remove_callback which is the one that should be removed.
The fix is to simple cache the connection removing the correct data before
checking if there is any filter left.
|
|
|
|
|
|
With g_dbus_add_signal_watch there is no need to register multiple filters
for dbus nor add matching rules manually.
|
|
|
|
|
|
|
|
|
