From 5a1d9522fa6cc40a14c88709ac5a81e959c230b5 Mon Sep 17 00:00:00 2001 From: Pawel Piech Date: Wed, 12 Mar 2008 19:35:38 +0000 Subject: [PATCH] [220446] Updated the "PDA Debugger Introduction" document. --- .../docs/pda/pda_tutorial_outline.html | 37 ++++++++++++++++++- 1 file changed, 35 insertions(+), 2 deletions(-) diff --git a/plugins/org.eclipse.dd.doc.dsf/docs/pda/pda_tutorial_outline.html b/plugins/org.eclipse.dd.doc.dsf/docs/pda/pda_tutorial_outline.html index ff01755a0c8..f87e58b80c8 100644 --- a/plugins/org.eclipse.dd.doc.dsf/docs/pda/pda_tutorial_outline.html +++ b/plugins/org.eclipse.dd.doc.dsf/docs/pda/pda_tutorial_outline.html @@ -2205,9 +2205,42 @@ it does not exist the update request fails. 
  • Lines 377-382 verify that only the data access attributes of the watchpoint were modified.
  • Lines 387 -398 re-insert the watchpoint which effectively updates -the watchpoint attributes.
    -
    • +the watchpoint attributes. +

    Listing Breakpoints

    +The PDA Breakpoints service tracks the inserted breakpoints using the fBreakpoints field.  Returning +the list of breakpoints only requires returning the current state of +this field.
    +

    Retrieving Breakpoint Detailed Data

    +The simple PDA debugger does not track detailed breakpoint data, such +has hit counts, addresses etc.  So this function simply returns an +error.
    +

    Breakpoints Mediator

    +With the APIs for managing IDE and Target-Side breakpoints clearly +defined, there is a need for a component which will keep the two sets +of breakpoint objects synchronized.  DSF provides a standard +BreakpointsMediator service to accomplish this task. 
    + + + + + + + + + +

    +
    Image 3: Mediating IDE and Target-Side +breakpoints
    +
    +
    +