Date: Sat Mar 31 20:01:43 CEST 2007
User: Derick Rethans
Directory: dbgp
Log Message:
- 7.6.1 Fixed breakpoint_set example and note that the breakpoint types
are listed above and not below.
Modified files:
dbgp/debugger_protocol.txt (version: 1.8)
[FILE: /dbgp/debugger_protocol.txt]
===================================================================
RCS file: cvstemp,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- dbgp/debugger_protocol.txt:1.7 Fri Jun 09 17:55:56 2006 GMT
+++ dbgp/debugger_protocol.txt Sat Mar 31 16:01:43 2007 GMT
@@ -966,7 +966,7 @@
where the arguments are:
================== =====================================================
- -t TYPE breakpoint *type*, see below for valid values
+ -t TYPE breakpoint *type*, see above for valid values
[required]
-s STATE breakpoint *state* [optional, defaults to "enabled"]
-f FILENAME the *filename* to which the breakpoint belongs
@@ -994,7 +994,7 @@
An example breakpoint_set command for a conditional breakpoint could look
like this::
- breakpoint_set -i 1 -f test.pl -n 20 -- base64($x > 3)
+ breakpoint_set -i 1 -t line -f test.pl -n 20 -- base64($x > 3)
A unique id for this breakpoint for this session is returned by the debugger
engine. This *session breakpoint id* is used by the IDE to identify the
@@ -2071,6 +2071,11 @@
A. ChangeLog
============
+2007-03-31
+
+- 7.6.1 Fixed breakpoint_set example and note that the breakpoint types
+ are listed above and not below.
+
2006-01-24
- 7.2.1 Added a description of the breakpoint_types feature.
Received on Sat Mar 31 2007 - 20:01:46 BST
This archive was generated by hypermail 2.2.0 : Sun Jun 24 2018 - 04:00:03 BST