Changes between Version 41 and Version 42 of NewGhciDebugger


Ignore:
Timestamp:
Apr 9, 2007 2:51:59 PM (8 years ago)
Author:
guest
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NewGhciDebugger

    v41 v42  
    7878 
    7979{{{ 
    80    :break OptionalModuleName 12 
    81 }}} 
    82  
    83 This 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 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? 
     80   :break <module>? <line_number> 
     81}}} 
     82 
     83This will activate the breakpoint which corresponds to the leftmost outermost breakable expression which ''begins'' and ''ends'' on line `<line_number>`, if such an expression exists. XXX If no such expression exists then what happens? Currently the debugger will 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? 
    8484 
    8585The syntax for setting breakpoints by line and column is: 
    8686 
    8787{{{ 
    88    :break OptionalModuleName 12 7 
    89 }}} 
    90  
    91 This will activate the breakpoint which corresponds to the ''smallest'' breakable expression which encloses the source location on 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. 
     88   :break <module>? <line> <column> 
     89}}} 
     90 
     91This will activate the breakpoint which corresponds to the ''smallest'' breakable expression which encloses the source location `(<line>, <column>)`, if such an expression exists. If no such expression exists the debugger will report an error message. 
    9292 
    9393The syntax for setting breakpoints by function name is: (XXX not yet implemented) 
    9494 
    9595{{{ 
    96    :break OptionalModuleName functionName 
    97 }}} 
    98  
    99 This 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? 
     96   :break <module>? <identifier> 
     97}}} 
     98 
     99This will activate the outermost breakpoint associated with the definition of `<identifier>`. If `<identifier>` is defined by multiple equations, the breakpoint will cover them all. This means the computation will stop whenever any of those equations is evaluated. XXX What about local functions? XXX What about functions defined in type classes (default methods) and instance declarations? 
    100100 
    101101=== Listing the active breakpoints ===