Changes between Version 10 and Version 11 of NewGhciDebugger


Ignore:
Timestamp:
Apr 8, 2007 4:50:40 PM (8 years ago)
Author:
guest
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NewGhciDebugger

    v10 v11  
    2727 4. List comprehensions. XXX check this one
    2828
     29We call the places where you can set breakpoints as '''breakable expressions''' (even if some of them aren't strictly expressions).
     30
    2931You can set a breakpoint in three ways:
    3032 1. By line number.
     
    3739
    3840{{{
    39    :break MyModuleName 12
     41   :break OptionalModuleName 12
    4042}}}
    4143
    42 This will activate the breakpoint which corresponds to the leftmost outermost complete (sub)expression which begins and ends on line 12 in the module called `MyModuleName`, if such an expression exists. XXX If no such expression exists then what happens? Currently the debugger will not set a breakpoint and report an error message, but perhaps it is nicer for it to probe a few lines ahead until it finds a breakable expression, or give up after some threshold number of lines?
     44This will activate the breakpoint which corresponds to the leftmost outermost breakable expression which begins and ends on line 12 in the module called `OptionalModuleName`, if such an expression exists. XXX If no such expression exists then what happens? Currently the debugger will not set a breakpoint and report an error message, but perhaps it is nicer for it to probe a few lines ahead until it finds a breakable expression, or give up after some threshold number of lines?
    4345
    4446The syntax for setting breakpoints by line and column is:
    4547
    4648{{{
    47    :break MyModuleName 12 7
     49   :break OptionalModuleName 12 7
    4850}}}
    4951
    50 This will activate the breakpoint which corresponds to the smallest (sub)expression which encloses the
     52This will activate the breakpoint which corresponds to the smallest breakable (sub)expression which encloses the source location: line 12, column 7, if such an expression exists. If no such expression exists the debugger will report an error message and no breakpoints will be set.
    5153
     54The syntax for setting breakpoints by function name is: (XXX not yet implemented)
     55
     56{{{
     57   :break OptionalModuleName functionName
     58}}}
     59
     60This will activate the outermost breakpoint associated with the definition of the function called `functionName`. The breakpoint will cover all the equations of a multi-equation function. XXX What about local functions? XXX What about functions defined in type classes (default methods) and instance declarations?
    5261
    5362=== Inspecting values ===