From bf99381351b802fb3348a24037898222aae631e2 Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Fri, 28 Mar 2003 05:42:19 +0000 Subject: 2003-03-28 Havoc Pennington * 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. --- bus/test.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'bus/test.c') diff --git a/bus/test.c b/bus/test.c index 24cc6efa..ea2c3a19 100644 --- a/bus/test.c +++ b/bus/test.c @@ -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)) ; } -- cgit