Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
|
|
When valgrinding tests it's useful to avoid using the shared bus, which
cannot be closed. Move all the essential shared-bus use into a test which
can be treated specially.
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=41129
Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
|
|
[rebased and added to run-test.sh -dbcw]
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=23633
|
|
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=40711
Reviewed-by: Dan Williams <dcbw@redhat.com>
|
|
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=40711
Reviewed-by: Dan Williams <dcbw@redhat.com>
|
|
The first part of the bug is that when NameOwnerChanged is received with
a dbus_g_proxy_new_for_peer (which has no name) alive, checking
whether it was affected by the NameOwnerChanged caused a NULL
dereference and segfault.
The second part of the bug is that if the last proxy in existence is
for a peer, when it was unregistered there would be no owner_match_rules,
causing a crash.
Both are exercised in the new test added here.
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=41126
Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
|
|
Most of this has been sitting in a branch since fd.o #30171; fixing
fd.o #40151, another case of library-user error leading to undefined
behaviour and a hard-to-diagnose crash, seems a good time to get this
merged.
Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=40151
Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
|
|
Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=40151
Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
|
|
Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=42532
|
|
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=38406
Reviewed-by: Cosimo Alfarano <cosimo.alfarano@collabora.co.uk>
|
|
This was the only use of DBUS_INCLUDEDIR, so remove that too.
Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=37789
|
|
Reviewed-by: Will Thompson <will.thompson@collabora.co.uk>
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=37789
|
|
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=27598
Reviewed-by: Robert Ancell <robert.ancell@canonical.com>
|
|
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=27598
Reviewed-by: Robert Ancell <robert.ancell@canonical.com>
|
|
Reviewed-by: Cosimo Alfarano <cosimo.alfarano@collabora.co.uk>
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=36793
|
|
dbus_connection_setup_with_g_main and dbus_server_setup_with_g_main are
intended to switch the setup to a new main loop context if they are
called with a context other than the one with which they were initially
called. However, this does not work in practice. The problem has to do
with libdbus maintaining a list of watches associated with the
connection. When dbus_connection_set_watch_functions is called, it
first adds the existing watches using the new function and data, then
removes the watches using the old function and data. Remove_watch calls
connection_setup_remove_watch, and the latter does not check that the
watch's connection setup matches the connection setup passed to it, so
it winds up removing the watch from the new connection setup. (The
watch has already been removed from the old setup at this point, as a
side effect of dbus_watch_set_data).
Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=30574>
Signed-off-by: Will Thompson <will.thompson@collabora.co.uk>
|
|
|
|
|
|
|
|
Add the new tests and *~ to the ignore list.
|
|
Ignore autoconf errors, autom4te.cache, some new generated files.
|
|
|