diff options
author | Havoc Pennington <hp@redhat.com> | 2003-03-28 05:42:19 +0000 |
---|---|---|
committer | Havoc Pennington <hp@redhat.com> | 2003-03-28 05:42:19 +0000 |
commit | bf99381351b802fb3348a24037898222aae631e2 (patch) | |
tree | aae0a9583e4d6aa559849e4326a3c9b2a7175015 /bus/test.c | |
parent | 574c258bc9304d51bf0cdd131a6473e6fc5b477f (diff) | |
download | dbus-bf99381351b802fb3348a24037898222aae631e2.tar.gz dbus-bf99381351b802fb3348a24037898222aae631e2.tar.bz2 dbus-bf99381351b802fb3348a24037898222aae631e2.zip |
2003-03-28 Havoc Pennington <hp@pobox.com>
* bus/test.c (bus_test_flush_bus): remove the sleep from here,
I think it may have just been superstition. Not sure.
* dbus/dbus-string.c (_dbus_string_base64_decode): catch some OOM
failures that were not being handled.
* dbus/dbus-auth.c (process_auth): fix a memleak in OOM handling
* dbus/dbus-memory.c: add ability to set number of mallocs in a
row that will fail on out-of-memory.
* dbus/dbus-internals.c (_dbus_test_oom_handling): convenience
function for testing out-of-memory handling.
* bus/config-loader-expat.c (memsuite): don't wrap the dbus
allocation functions, they do map exactly to the expat ones.
Diffstat (limited to 'bus/test.c')
-rw-r--r-- | bus/test.c | 6 |
1 files changed, 4 insertions, 2 deletions
@@ -267,7 +267,6 @@ bus_test_client_listed (DBusConnection *connection) return FALSE; } - void bus_test_flush_bus (BusContext *context) { @@ -276,11 +275,14 @@ bus_test_flush_bus (BusContext *context) * one end of the debug pipe to come out the other end... * a more robust setup would be good. Blocking on the other * end of pipes we've pushed data into or something. + * A simple hack might be to just make the debug server always + * poll for read on the other end of the pipe after writing. */ - while (bus_loop_iterate (FALSE)) ; +#if 0 _dbus_sleep_milliseconds (15); +#endif while (bus_loop_iterate (FALSE)) ; } |