291e414a9e
Most of the debug events had their own message, but some were grouped into this `stopped' message with a `why' field to describe what kind of event it actually was. Hence the user had to check two levels until they could know what event occurred. So I got rid of this message and provided separate messages for the concerned events. * Got rid of B_DEBUG_MESSAGE_GET_WHY_STOPPED and introduced B_DEBUG_MESSAGE_GET_CPU_STATE which is pretty much the same. * Put B_DEBUG_MESSAGE_RUN_THREAD and B_DEBUG_MESSAGE_STEP_THREAD into a single B_DEBUG_MESSAGE_CONTINUE_THREAD message with a boolean `single_step' field. * get_debug_why_stopped_string() -> get_debug_message_string(). git-svn-id: file:///srv/svn/repos/haiku/trunk/current@11712 a95241bf-73f2-0310-859d-f6bbb57e9c96 |
||
---|---|---|
.. | ||
cpp | ||
gnu | ||
libs | ||
os | ||
posix | ||
private | ||
tools |