Attachment 28990 Details for Bug 23584 – Process log with DBUS_VERBOSE set showing missed sent message

Process log with DBUS_VERBOSE set showing missed sent message

bug.log (text/plain), 7.27 KB, created by Patrick Allison on 2009-08-28 14:16:47 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Patrick Allison

Created: 2009-08-28 14:16:47 UTC

Size: 7.27 KB

patch

obsolete

>14802: 0xb72fab90: _dbus_connection_handle_watch start
>14802: 0xb72fab90:   LOCK: _dbus_connection_handle_watch
>14802: 0xb72fab90:   UNLOCK: _dbus_connection_acquire_io_path
>14802: 0xb72fab90: _dbus_connection_acquire_io_path locking io_path_mutex
>14802: 0xb72fab90: _dbus_connection_acquire_io_path start connection->io_path_acquired = 0 timeout = -1
>14802: 0xb72fab90: _dbus_connection_acquire_io_path end connection->io_path_acquired = 1 we_acquired = 1
>14802: 0xb72fab90: _dbus_connection_acquire_io_path unlocking io_path_mutex
>14802: 0xb72fab90:   LOCK: _dbus_connection_acquire_io_path
>14802: 0xb72fab90: handling read watch 0x9887680 flags = 1
>14802: 0xb72fab90: do_reading: fd = 3
>14802: 0xb72fab90: check_read_watch: fd = 3
>14802: 0xb72fab90:   setting read watch enabled = 1
>14802: 0xb72fab90:   UNLOCK: protected_change_watch
>14802: 0xb72fab90:   LOCK: protected_change_watch
>14802: 0xb72fab90:  read 185 bytes
>14802: 0xb72fab90: have 185 bytes, need body 17 + header 168 = 185
>14802: 0xb72fab90: validating body from pos 0 len 185 sig 'yyyyuua(yv)'
>14802: 0xb72fab90: p = 0x9888b27 end = 0x9888b49 claimed_len 1
>14802: 0xb72fab90: initially caching field 1
>14802: 0xb72fab90: initially caching field 6
>14802: 0xb72fab90: initially caching field 2
>14802: 0xb72fab90: initially caching field 3
>14802: 0xb72fab90: initially caching field 8
>14802: 0xb72fab90: initially caching field 7
>14802: 0xb72fab90: validating body from pos 168 len 17 sig 's'
>14802: 0xb72fab90: Loaded message 0x9889318
>14802: 0xb72fab90: queueing received message 0x9889318
>
>3073354640: Dispatcher::on_wakeup_main
>
>14802: 0xb7afbb90: dbus_connection_get_dispatch_status start
>14802: 0xb7afbb90:   LOCK: dbus_connection_get_dispatch_status
>14802: 0xb72fab90: Message 0x9889318 (1 /amber/AmCtl amber.AmCtl.server.acquisition unregister_service 's' reply to 0) added to incoming queue 0x98879d0, 1 incoming
>14802: 0xb72fab90: check_read_watch: fd = 3
>14802: 0xb72fab90:   setting read watch enabled = 1
>14802: 0xb72fab90:   UNLOCK: protected_change_watch
>14802: 0xb7afbb90:   UNLOCK: dbus_connection_get_dispatch_status
>
>3081747344: Dispatch Status: 0   Hints: DISPATCH_DATA_REMAINS=0
>
>14802: 0xb7afbb90: dbus_connection_get_dispatch_status start
>14802: 0xb7afbb90:   LOCK: dbus_connection_get_dispatch_status
>14802: 0xb7afbb90:   UNLOCK: dbus_connection_get_dispatch_status
>14802: 0xb7afbb90: dbus_connection_dispatch
>14802: 0xb7afbb90:   LOCK: dbus_connection_dispatch
>14802: 0xb7afbb90:   UNLOCK: _dbus_connection_acquire_dispatch
>14802: 0xb7afbb90: _dbus_connection_acquire_dispatch locking dispatch_mutex
>14802: 0xb7afbb90: _dbus_connection_acquire_dispatch unlocking dispatch_mutex
>14802: 0xb7afbb90:   LOCK: _dbus_connection_acquire_dispatch
>14802: 0xb7afbb90: Message 0x9889318 (1 /amber/AmCtl amber.AmCtl.server.acquisition unregister_service 's') removed from incoming queue 0x98879d0, 0 incoming
>14802: 0xb7afbb90:  dispatching message 0x9889318 (1 amber.AmCtl.server.acquisition unregister_service 's')
>14802: 0xb7afbb90:   UNLOCK: dbus_connection_dispatch
>14802: 0xb7afbb90:   running filter on message 0x9889318
>14802: 0xb7afbb90:   LOCK: dbus_connection_get_data
>14802: 0xb7afbb90:   UNLOCK: dbus_connection_get_data
>
>14802: 0xb7afbb90:   LOCK: dbus_connection_dispatch
>14802: 0xb7afbb90:   running object path dispatch on message 0x9889318 (1 amber.AmCtl.server.acquisition unregister_service 's')
>14802: 0xb7afbb90: 1 handlers in the path tree for this message
>14802: 0xb7afbb90: unlock _dbus_object_tree_dispatch_and_unlock
>14802: 0xb7afbb90:   UNLOCK: _dbus_connection_unlock
>14802: 0xb7afbb90:   LOCK: dbus_connection_get_data
>14802: 0xb7afbb90:   UNLOCK: dbus_connection_get_data
>
>3081747344: Method<T_return, T_arg1>::handle_call_message   method=unregister_service
>3081747344: Connection::send
>
>14802: 0xb7afbb90:   LOCK: dbus_connection_send
>14802: 0xb7afbb90: Message 0x98993b8 (2 no path no interface no member 'i') for :1.21 added to outgoing queue 0x98879d0, 1 pending to send
>14802: 0xb7afbb90: Message 0x98993b8 serial is 62
>14802: 0xb7afbb90: _dbus_connection_do_iteration_unlocked start
>14802: 0xb7afbb90:   UNLOCK: _dbus_connection_acquire_io_path
>14802: 0xb7afbb90: _dbus_connection_acquire_io_path locking io_path_mutex
>14802: 0xb7afbb90: _dbus_connection_acquire_io_path start connection->io_path_acquired = 1 timeout = 0
>14802: 0xb7afbb90: _dbus_connection_acquire_io_path waiting 0 for IO path to be acquirable
>14802: 0xb7afbb90: _dbus_connection_acquire_io_path end connection->io_path_acquired = 1 we_acquired = 0
>14802: 0xb7afbb90: _dbus_connection_acquire_io_path unlocking io_path_mutex
>14802: 0xb7afbb90:   LOCK: _dbus_connection_acquire_io_path
>14802: 0xb7afbb90: _dbus_connection_do_iteration_unlocked end
>
>3081747344: Dispatcher::on_wakeup_main
>
>14802: 0xb7afbb90: _dbus_connection_send_preallocated_and_unlock middle
>14802: 0xb7afbb90: dispatch status = complete is_connected = 1
>14802: 0xb7afbb90:   UNLOCK: _dbus_connection_update_dispatch_status_and_unlock
>
>3081747344: Object::handle_message: message was handled
>3081747344: ObjectPathHandler::message_handler_callback: result = 0
>
>14802: 0xb7afbb90:   LOCK: _dbus_connection_lock
>14802: 0xb7afbb90: unlock _dbus_object_tree_dispatch_and_unlock
>14802: 0xb7afbb90:   UNLOCK: _dbus_connection_unlock
>14802: 0xb7afbb90:   LOCK: dbus_connection_dispatch
>14802: 0xb7afbb90: object tree handled message in dispatch
>14802: 0xb7afbb90:  ... done dispatching in dbus_connection_dispatch
>14802: 0xb7afbb90: _dbus_connection_release_dispatch locking dispatch_mutex
>14802: 0xb7afbb90: _dbus_connection_release_dispatch unlocking dispatch_mutex
>14802: 0xb7afbb90: dbus_connection_dispatch before final status update
>14802: 0xb7afbb90: dispatch status = complete is_connected = 1
>14802: 0xb7afbb90:   UNLOCK: _dbus_connection_update_dispatch_status_and_unlock
>14802: 0xb7afbb90: dbus_connection_get_dispatch_status start
>14802: 0xb7afbb90:   LOCK: dbus_connection_get_dispatch_status
>14802: 0xb7afbb90: dispatch status = complete is_connected = 1
>14802: 0xb7afbb90:   UNLOCK: dbus_connection_get_dispatch_status
>14802: 0xb7afbb90: dbus_connection_get_dispatch_status start
>14802: 0xb7afbb90:   LOCK: dbus_connection_get_dispatch_status
>14802: 0xb7afbb90: dispatch status = complete is_connected = 1
>14802: 0xb7afbb90:   UNLOCK: dbus_connection_get_dispatch_status
>14802: 0xb7afbb90: dbus_connection_get_dispatch_status start
>14802: 0xb7afbb90:   LOCK: dbus_connection_get_dispatch_status
>14802: 0xb7afbb90: dispatch status = complete is_connected = 1
>14802: 0xb7afbb90:   UNLOCK: dbus_connection_get_dispatch_status
>
>3081747344: Dispatch Status: 1   Hints: DISPATCH_DATA_REMAINS=0
>
>14802: 0xb7afbb90: dbus_connection_get_dispatch_status start
>14802: 0xb7afbb90:   LOCK: dbus_connection_get_dispatch_status
>14802: 0xb7afbb90: dispatch status = complete is_connected = 1
>14802: 0xb7afbb90:   UNLOCK: dbus_connection_get_dispatch_status
>14802: 0xb72fab90:   LOCK: protected_change_watch
>14802: 0xb72fab90: _dbus_connection_release_io_path locking io_path_mutex
>14802: 0xb72fab90: _dbus_connection_release_io_path start connection->io_path_acquired = 1
>14802: 0xb72fab90: _dbus_connection_release_io_path unlocking io_path_mutex
>14802: 0xb72fab90: _dbus_connection_handle_watch middle
>14802: 0xb72fab90: dispatch status = complete is_connected = 1
>14802: 0xb72fab90:   UNLOCK: _dbus_connection_update_dispatch_status_and_unlock
>14802: 0xb72fab90: _dbus_connection_handle_watch end
>

Actions: View

Attachments on bug 23584: 28990

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.