mirror of
https://gitlab.freedesktop.org/dbus/dbus.git
synced 2025-12-30 08:20:11 +01:00
The exact failure mode reported in dbus/dbus#457 is quite difficult to achieve in a reliable way in a unit test, because we'd have to send enough messages to a client to fill up its queue, then stop that client from draining its queue, while still triggering a message that gets a reply from the bus driver. However, we can trigger the same crash in a slightly different way by not allowing the client to receive a particular message. I chose NameAcquired. Signed-off-by: Simon McVittie <smcv@collabora.com> |
||
|---|---|---|
| .. | ||
| auth | ||
| equiv-config-files | ||
| installable | ||
| invalid-config-files | ||
| invalid-messages | ||
| invalid-service-files-system | ||
| sha-1 | ||
| systemd-activation | ||
| valid-config-files | ||
| valid-config-files-system | ||
| valid-messages | ||
| valid-service-files | ||
| valid-service-files-system | ||
| copy_data_for_tests.py | ||
| dbus-installed-tests.aaprofile.in | ||
| meson.build | ||