Changes between Version 42 and Version 43 of NewGhciDebugger


Ignore:
Timestamp:
Apr 9, 2007 2:55:33 PM (7 years ago)
Author:
guest
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NewGhciDebugger

    v42 v43  
    1616Setting breakpoints: 
    1717{{{ 
    18    :break <module>? <line_number> 
    19    :break <module>? <line_number> <column_number> 
    20    :break <module>? <function_name> 
     18   :break <module>? <line> 
     19   :break <module>? <line> <column> 
     20   :break <module>? <identifier> 
    2121}}} 
    2222Listing breakpoints: 
     
    2626Deleting breakpoints: 
    2727{{{ 
    28    :delete <break_id> ... <break_id> 
     28   :delete <break_number> ... <break_number> 
    2929   :delete * 
    3030}}} 
     
    7878 
    7979{{{ 
    80    :break <module>? <line_number> 
    81 }}} 
    82  
    83 This 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? 
     80   :break <module>? <line> 
     81}}} 
     82 
     83This will activate the breakpoint which corresponds to the leftmost outermost breakable expression which ''begins'' and ''ends'' on the line indicated by the `<line>` parameter, 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: 
     
    121121You can delete any active breakpoint with the `:delete` command. Breakpoints are refered to by their unique number which is displayed by the `:show breaks` command (see above). You can refer to more than one breakpoint at a time, for example: 
    122122{{{ 
    123    :delete 2 12 
    124 }}} 
    125 This will delete the breakpoints numbered 2 and 12. If you specify a breakpoint which does not exist, the debugger will simply ignore it. 
     123   :delete <break_number> ... <break_number> 
     124}}} 
     125This will delete all the breakpoints which are identified by the numbers `<break_number> ... <break_number>`. If you specify a breakpoint which does not exist, the debugger will simply ignore it. 
    126126 
    127127You can also delete all the active breakpoints by giving the asterisk as an argument to `delete`, like so: 
     
    140140}}} 
    141141 
    142 The string `*Main>` is GHCi's prompt marker. Note that it can change depending on what modules you have loaded.  
     142The string "`*Main>`" is GHCi's prompt marker. Note that it can change depending on what modules you have loaded.  
    143143 
    144144All the normal GHCi commands work at the prompt, including the evaluation of arbitrary expressions. In addition to the normal prompt behaviour, the local variables of the breakpoint are also made available. For instance, in the above example the variable `f` is a function from booleans to booleans, and we can apply it to an argument in the usual way: