[haiku-bugs] Re: [Haiku] #10037: ActivityMonitor replicant locks up Tracker upon startup

  • From: "bonefish" <trac@xxxxxxxxxxxx>
  • Date: Mon, 30 Sep 2013 15:31:31 -0000

#10037: ActivityMonitor replicant locks up Tracker upon startup
-------------------------+----------------------------
   Reporter:  stippi     |      Owner:  nobody
       Type:  bug        |     Status:  new
   Priority:  normal     |  Milestone:  R1
  Component:  - General  |    Version:  R1/Development
 Resolution:             |   Keywords:
 Blocked By:             |   Blocking:
Has a Patch:  0          |   Platform:  All
-------------------------+----------------------------

Comment (by bonefish):

 I don't have an explanation for the behavior, but I would recommend
 employing the kernel tracing feature to track this down. There's already
 some output prepared in `BMessage::_SendMessage()`, though it might be
 helpful to add the reply port/token as well. Then just enabled kernel
 tracing for `BMessage` (`BMESSAGE_TRACING`), ideally also for syscalls
 (`SYSCALL_TRACING`), and for team events (`TEAM_TRACING`) for good
 measure. This should allow following the message trail, with sufficient
 additional information to see what's going on. Stack traces in KDL
 (particularly for the input server, which is otherwise somewhat
 inconvenient to debug) help as well. Obviously you can also add other
 `ktrace_printf()`s at strategic points.

--
Ticket URL: <http://dev.haiku-os.org/ticket/10037#comment:1>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: