1. 12 Feb, 2016 1 commit
  2. 11 Feb, 2016 1 commit
  3. 14 May, 2015 1 commit
  4. 12 May, 2015 1 commit
  5. 02 Mar, 2015 1 commit
  6. 20 Feb, 2015 1 commit
  7. 13 Feb, 2015 1 commit
  8. 03 Feb, 2015 1 commit
  9. 15 Sep, 2014 2 commits
  10. 28 Apr, 2014 1 commit
  11. 16 Sep, 2013 1 commit
  12. 29 Aug, 2013 1 commit
  13. 28 Jun, 2013 1 commit
  14. 17 Jun, 2013 2 commits
  15. 13 May, 2013 1 commit
  16. 09 May, 2013 1 commit
  17. 13 Aug, 2012 2 commits
  18. 21 Feb, 2012 1 commit
    • Simon McVittie's avatar
      Distinguish between two flavours of mutex · 8a58250a
      Simon McVittie authored
      dbus-threads.h warns that recursive pthreads mutexes are not compatible
      with our expectations for condition variables. However, the only two
      condition variables we actually use only have their corresponding
      mutexes locked briefly (and we don't call out to user code from there),
      so the mutexes don't need to be recursive anyway. That's just as well,
      because it turns out our implementation of recursive mutexes on
      pthreads is broken!
      
      The goal here is to be able to distinguish between "cmutexes" (mutexes
      compatible with a condition variable) and "rmutexes" (mutexes which
      are recursive if possible, to avoid deadlocking if we hold them while
      calling user code).
      
      This is complicated by the fact that callers are not guaranteed to have
      provided us with both versions of mutexes, so we might have to implement
      one by using the other (in particular, DBusRMutex *aims to be*
      recursive, it is not *guaranteed to be* recursive).
      
      Bug: https://bugs.freedesktop.org/show_bug.cgi?id=43744Signed-off-by: default avatarSimon McVittie <simon.mcvittie@collabora.co.uk>
      Reviewed-by: Thiago Macieira's avatarThiago Macieira <thiago@kde.org>
      8a58250a
  19. 13 Feb, 2012 1 commit
    • Simon McVittie's avatar
      Provide a hook to allow refcounting to be traced · 566a8416
      Simon McVittie authored
      This is designed to be used from a wrapper function, partly to supply
      the same arguments every time for a particular class of object, and partly
      to provide a more specific gdb breakpoint. It has several purposes:
      
      * when under gdb, provide a function which can be used in breakpoints
      * when not under valgrind and DBUS_MESSAGE_TRACE=1 is set, emit a
        _dbus_verbose when a message's refcount changes
      * when under valgrind and DBUS_MESSAGE_TRACE=1 is set, emit a
        VALGRIND_PRINTF_BACKTRACE when a message's refcount changes,
        which lets you see the complete history of each message to track down
        reference leaks
      
      Compile-time support is currently conditional on DBUS_ENABLE_VERBOSE_MODE,
      but could be separated out if desired.
      
      Bug: https://bugs.freedesktop.org/show_bug.cgi?id=37286Signed-off-by: default avatarSimon McVittie <simon.mcvittie@collabora.co.uk>
      Reviewed-by: Lennart Poettering's avatarLennart Poettering <lennart@poettering.net>
      566a8416
  20. 10 Feb, 2012 1 commit
  21. 04 Jan, 2012 1 commit
    • Simon McVittie's avatar
      Revert all changes since a36d4918 · 5df8c3db
      Simon McVittie authored
      Someone seems to have merged part of master into 1.4. Again. Let's go
      back to the "last known good" point (the branch-point of some 1.4
      branches I had locally), then we can cherry-pick the changes that
      should have gone in.
      5df8c3db
  22. 19 Sep, 2011 1 commit
  23. 11 Aug, 2011 1 commit
  24. 11 Jun, 2010 1 commit
  25. 03 May, 2010 1 commit
  26. 22 Mar, 2010 1 commit
  27. 19 Mar, 2010 1 commit
  28. 25 Feb, 2010 1 commit
  29. 19 Dec, 2009 1 commit
  30. 30 Nov, 2009 1 commit
  31. 14 Jul, 2009 1 commit
  32. 10 Jul, 2009 1 commit
  33. 20 May, 2009 1 commit
    • Lennart Poettering's avatar
      atomic: implement atomic operations based on gcc's __sync extension · 9293e823
      Lennart Poettering authored
      Newer gccs and intel ccs support a __sync extension for making use of
      atomic operations. This patch replaces the handcrafted x86 atomic
      operation support with usage of __sync.
      
      __sync is supported by more processors and by more compilers than the
      old assembler code. Also, this extension has been available on gcc for
      quite a while now for x86, so replacing the old assembler code should
      only be a loss when very old compiilers are used.
      9293e823
  34. 03 Oct, 2007 1 commit
  35. 14 Jul, 2007 1 commit
  36. 13 Dec, 2006 1 commit
  37. 15 Nov, 2006 1 commit
    • Havoc Pennington's avatar
      2006-11-14 Havoc Pennington <hp@redhat.com> · dbc061b8
      Havoc Pennington authored
      	* dbus/dbus-internals.c (_dbus_generate_uuid): The spec said the
      	UUID had the timestamp last, but the implementation had it first;
      	move it to last since I think it's a tiny bit nicer (easier to
      	compare at a glance, faster to sort, less code), and will not
      	cause any practical compatibility problems. Also, always convert
      	the timestamp to big endian.
      
      	* doc/dbus-specification.xml: Clean up the docs on the UUID.
      
      	* tools/dbus-uuidgen.1: more prominently say it is not suitable
      	as a replacement for regular uuidgen/RFC4122.
      dbc061b8