Attachment 84308 Details for Bug 68303 – [PATCH 07/10] dbus-server.c: trace all server ref count change events

[patch] [PATCH 07/10] dbus-server.c: trace all server ref count change events

0007-dbus-server.c-trace-all-server-ref-count-change-even.patch (text/plain), 1.23 KB, created by Chengwei Yang on 2013-08-20 07:44:38 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Chengwei Yang

Created: 2013-08-20 07:44:38 UTC

Size: 1.23 KB

patch

obsolete

>From 60788ddd043efcb5d2fe97966498b451dab55fe3 Mon Sep 17 00:00:00 2001
>From: Chengwei Yang <chengwei.yang@intel.com>
>Date: Tue, 20 Aug 2013 15:10:39 +0800
>Subject: [PATCH 07/10] dbus-server.c: trace all server ref count change
> events
>
>Two small changes for this topic.
>* trace server init event
>* call dbus_server_ref() to trace server ref count change event because
>  it will call dbus_server_unref later
>---
> dbus/dbus-server.c |    5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
>diff --git a/dbus/dbus-server.c b/dbus/dbus-server.c
>index 02cf5a3..60ea5e9 100644
>--- a/dbus/dbus-server.c
>+++ b/dbus/dbus-server.c
>@@ -116,6 +116,9 @@ _dbus_server_init_base (DBusServer             *server,
> 
>   server->vtable = vtable;
>   _dbus_atomic_inc (&server->refcount);
>+  _dbus_server_trace_ref (server, 0,
>+                          _dbus_atomic_get (&server->refcount),
>+                          "init_base");
> 
>   server->address = NULL;
>   server->watches = NULL;
>@@ -773,7 +776,7 @@ dbus_server_disconnect (DBusServer *server)
>   _dbus_return_if_fail (server != NULL);
>   _dbus_return_if_fail (_dbus_atomic_get (&server->refcount) > 0);
> 
>-  _dbus_atomic_inc (&server->refcount);
>+  dbus_server_ref (server);
> 
>   SERVER_LOCK (server);
> 
>-- 
>1.7.9.5
>

Actions: View | Splinter Review

Attachments on bug 68303: 84302 | 84303 | 84304 | 84305 | 84306 | 84307 | 84308 | 84309 | 84310 | 84311 | 84503 | 84504 | 84505 | 84507 | 84508 | 84509 | 84510

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.