summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* spec v0.18 and D-Bus 1.5.6dbus-1.5.6Simon McVittie2011-07-293-4/+23
|
* spec: mention that buses may have a security policy, but leave it ↵Simon McVittie2011-07-291-0/+8
| | | | | | | implementation-specific Bug: https://bugs.freedesktop.org/show_bug.cgi?id=39450 Reviewed-by: Thiago Macieira <thiago@kde.org>
* Move the explanation of message routing to the Message Routing section, ↵Simon McVittie2011-07-291-52/+56
| | | | | | | leaving behind a summary Bug: https://bugs.freedesktop.org/show_bug.cgi?id=39450 Reviewed-by: Thiago Macieira <thiago@kde.org>
* Define eavesdropping, and document the eavesdrop matchSimon McVittie2011-07-291-0/+60
| | | | | Bug: https://bugs.freedesktop.org/show_bug.cgi?id=39450 Reviewed-by: Thiago Macieira <thiago@kde.org>
* spec: define unicast messages and broadcast signals, and explicitly allow ↵Simon McVittie2011-07-291-3/+21
| | | | | | | | | | | unicast signals I believe that the wording of the spec has always allowed unicast signals, but most bindings assume that signals are broadcasts, so it seems worth saying specifically that this feature exists and can be useful. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=39450 Reviewed-by: Thiago Macieira <thiago@kde.org>
* spec: make the Match Rules section true againSimon McVittie2011-07-291-8/+13
| | | | | | | | | | The spec previously claimed that only messages matching the client's match rules would be received. This is not actually true: messages listing a client as their DESTINATION are always delivered (security policy permitting). Bug: https://bugs.freedesktop.org/show_bug.cgi?id=39450 Reviewed-by: Thiago Macieira <thiago@kde.org>
* Merge branch 'dbus-1.4'Simon McVittie2011-07-290-0/+0
|\ | | | | | | | | | | Conflicts: NEWS configure.ac
| * micro versionSimon McVittie2011-07-291-1/+1
| |
| * 1.4.14dbus-1.4.14Simon McVittie2011-07-292-2/+4
| |
* | NEWS for 1.5Simon McVittie2011-07-291-1/+7
| |
* | Merge branch 'dbus-1.4'Simon McVittie2011-07-294-26/+46
|\ \ | |/ | | | | | | Conflicts: NEWS
| * NEWSSimon McVittie2011-07-291-2/+8
| |
| * Implement _dbus_atomic_get directly, rather than via inc + decSimon McVittie2011-07-293-24/+38
| | | | | | | | | | | | | | | | The Windows implementation is untested, but does at least (cross-)compile, and matches what GLib does. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=38005 Reviewed-by: Lennart Poettering <lennart@poettering.net>
* | Remove remnants of dbus-viewerSimon McVittie2011-07-293-626/+0
| | | | | | | | | | Parts of it were already missing, it wasn't compiled, and it depends on dbus-glib and Gtk.
* | tools: use AM_CPPFLAGS, and wrap its linesSimon McVittie2011-07-291-1/+7
| |
* | test, test/name-test: remove SOURCES where they can be inferred from the ↵Simon McVittie2011-07-292-57/+0
| | | | | | | | name of the executable
* | test/name-test: remove useless CFLAGSSimon McVittie2011-07-291-4/+0
| |
* | test/name-test: use AM_CPPFLAGS instead of INCLUDESSimon McVittie2011-07-291-2/+6
| |
* | dbus: use AM_CPPFLAGSSimon McVittie2011-07-291-4/+13
| |
* | test: promote GLIB_CFLAGS, DBUS_GLIB_CFLAGS to top level and use AM_CPPFLAGSSimon McVittie2011-07-291-6/+5
| | | | | | | | | | | | | | | | INCLUDES is a deprecated way to get the same effect as AM_CPPFLAGS. It's harmless to add extra -I directories to all the tests, even those that use neither GLib nor dbus-glib, so we can simplify by setting these AM_CPPFLAGS for the whole directory.
* | test: reverse assumption regarding static/dynamic linkingSimon McVittie2011-07-291-3/+10
| | | | | | | | | | | | | | If we change the default assumption to be that new tests will be dynamically-linked to libdbus, those tests can be useful for installcheck or even for installation. Accordingly, explicitly use new variable $(static_cppflags) for all tests that need static linking.
* | bus: use AM_CPPFLAGS to simplify preprocessor invocationSimon McVittie2011-07-291-8/+9
| | | | | | | | | | | | Everything in this directory is statically linked to libdbus-internal, so we can make -DDBUS_STATIC_BUILD global. Also, merge INCLUDES into AM_CPPFLAGS (it's an older name for the same functionality).
* | Simplify linking for tests that use libdbus-testutilsSimon McVittie2011-07-294-24/+24
| | | | | | | | | | | | | | | | | | | | This is the library used by tests that link libdbus-internal and DBusLoop. By linking libdbus-internal into it, we can avoid having to repeat that dependency all over the place - libtool and cmake both know how to follow recursive dependencies. In cmake, also use libdbus-testutils for more tests, in preference to repeating its source files.
* | Don't explicitly link thread and network libs into various testsSimon McVittie2011-07-294-20/+16
| | | | | | | | | | | | | | | | | | These tests get everything they need from the public or internal API of libdbus-internal.la, and libtool knows how to pull in libraries' dependencies, so we don't need explicit linking. spawn-test and break-loader don't actually need test-utils.[ch] either.
* | Rename DBUS_CLIENT_LIBS to LIBDBUS_LIBS to more accurately reflect its meaningSimon McVittie2011-07-294-6/+6
| | | | | | | | | | | | This does still need to be in configure.ac, because it's common to dbus/Makefile.am (linking the static/shared library) and dbus-1*.pc.in (telling static library users which additional libraries they must link).
* | tools: simplify linkingSimon McVittie2011-07-291-4/+13
| | | | | | | | | | | | | | | | | | * dbus-send, dbus-uuidgen only need to link libdbus; libtool knows what extra libraries libdbus depends on * dbus-monitor uses a Winsock header (on Windows) so it needs NETWORK_libs,but still doesn't need threads * dbus-launch needs X (on Unix) but doesn't directly need threads or networking
* | tools: put bin_PROGRAMS one per line, eliminate unnecessary variableSimon McVittie2011-07-291-4/+10
| |
* | Move knowledge of what the bus daemon/launcher need to link into bus/Simon McVittie2011-07-292-11/+15
| |
* | Substitute cflags/libs per-librarySimon McVittie2011-07-291-1/+10
| | | | | | | | | | | | This means each module can link whatever it needs to, localizing the knowledge of which module needs which libraries into its own Makefile.am.
* | Stop defining DBUS_API_SUBJECT_TO_CHANGESimon McVittie2011-07-291-1/+1
| | | | | | | | Seriously.
* | dbus: remove export_symbols_internal, it will always be emptySimon McVittie2011-07-291-6/+0
| | | | | | | | The whole point of libdbus-internal.la is that it exports all its symbols.
* | Simplify linking by moving -export-dynamic to AM_LDFLAGSSimon McVittie2011-07-295-34/+25
| |
* | Remove DBUS_GLIB_CFLAGS from name-test subdirectory (not used/needed)Simon McVittie2011-07-291-1/+1
| | | | | | | | This appears to be left over from when dbus-glib was part of dbus.
* | Remove DBUS_CLIENT_CFLAGS, which is always emptySimon McVittie2011-07-294-5/+2
| |
* | Remove DBUS_TEST_CFLAGS, which is emptySimon McVittie2011-07-293-4/+2
| |
* | Remove leftover reference to dbus-md5.[ch]Simon McVittie2011-07-291-3/+0
| |
* | Remove declarations for tests that no longer existSimon McVittie2011-07-291-2/+0
| |
* | Fix compilation for removal of link cacheSimon McVittie2011-07-293-14/+4
| |
* | Merge branch 'dbus-1.4'Lennart Poettering2011-07-281-4/+0
|\ \ | |/
| * sysdeps-unix: remove some redundant assignmentsLennart Poettering2011-07-281-4/+0
| |
* | Merge branch 'dbus-1.4'Lennart Poettering2011-07-282-5/+15
|\ \ | |/
| * activation: add /lib/dbus-1/system-services to the search path for servicesLennart Poettering2011-07-282-5/+15
| | | | | | | | | | | | | | | | | | | | In order to allow D-Bus usage during early boot (where /usr is not accessible) also search for bus activation files in /lib/dbus-1/system-services/. This is only a first step in the right direction, before we really can boot without /usr we'd need to move all current activation files (or possibly replace /usr/dbus-1/system-services to a symlink to /lib/dbus-1/system-services).
* | _dbus_message_remove_counter: remove ability to return the linkSimon McVittie2011-07-283-15/+5
| | | | | | | | | | Reviewed-by: Colin Walters <walters@verbum.org> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34393
* | Add a regression test that can reproduce fd.o #34393Simon McVittie2011-07-282-16/+77
| | | | | | | | | | | | | | | | | | The number of messages is arbitrary; the more messages, the more likely the crash is. 2000 messages seem to cause it reliably on this laptop, but I've set it to 10000 to be safe. Reviewed-by: Colin Walters <walters@verbum.org> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34393
* | Remove the per-connection link cacheSimon McVittie2011-07-281-50/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | With fd.o#34393 fixed, retaking the lock to cache unused links significantly adds to locking overhead (-18% throughput in a synthetic benchmark on an ARM device). The cache is also unlimited in size, and probably contributes to memory growth and fragmentation by not being under the system malloc's control. Fixing fd.o #34393, but also dropping this cache entirely, turns out to lead to a 5% increase in throughput on the same synthetic benchmark. Reviewed-by: Colin Walters <walters@verbum.org> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34393
* | dbus_connection_dispatch: avoid freeing UnknownMethod reply until we unlockSimon McVittie2011-07-281-4/+16
| | | | | | | | | | Reviewed-by: Colin Walters <walters@verbum.org> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34393
* | _dbus_connection_peer_filter_unlocked_no_update: delay freeing replySimon McVittie2011-07-281-41/+40
| | | | | | | | | | | | | | | | Finalizing the reply could conceivably call callbacks, so wait til we unlock. Reviewed-by: Colin Walters <walters@verbum.org> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34393
* | Don't finalize sent or dispatched messages while under the connection lockSimon McVittie2011-07-282-13/+62
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Finalizing a message can trigger callbacks; that's bad, if we have a connection locked. In particular, if a message is received by the "left side", passed to the "right side" and sent (as in test/relay.c (see the diagram there) or in dbus-daemon), then finalizing that message could result in the live messages counter for the left side, and the outgoing messages counter for the right side, both being decremented while under either side's lock. After a message is dispatched on the left side, finalizing it now drops the lock temporarily, to avoid this problem. After a message is sent on the right side, finalizing it is now deferred until the right side unlocks, by moving it to a new queue of "expired messages" which is automatically cleared every time we release the lock. The "live messages" counter for the "left" connection will now explicitly take the left connection's lock before decrementing, to avoid manipulating watches without a lock. Reviewed-by: Colin Walters <walters@verbum.org> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34393
* | Don't inline the contents of _dbus_connection_unlockSimon McVittie2011-07-281-6/+8
| | | | | | | | | | | | | | | | It's about to become more complex, to handle delayed deallocation of messages in order to avoid triggering callbacks while locked. Reviewed-by: Colin Walters <walters@verbum.org> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34393
* | When attaching counters to messages, don't automatically notify callbacksSimon McVittie2011-07-283-3/+23
| | | | | | | | | | | | | | | | | | In all the places where counters are added, we're under a lock. The caller knows what effect adding the counter might have, and can replicate it in a lock-safe way if necessary. Reviewed-by: Colin Walters <walters@verbum.org> Bug: https://bugs.freedesktop.org/show_bug.cgi?id=34393
View Lorry Controller Status