Changes between Version 7 and Version 8 of HBDBPlanning

Timestamp:

08/06/11 22:27:36 (10 years ago)

Author:

soh_cah_toa

Comment:

Started dividing features into separate groups.

HBDBPlanning

@@ -1 @@
-This page exists to help plan out soh_cah_toa's GSoC project.  Unfortunately it turns out to depend heavily on parts of imcc which were substantially more broken than anyone realized.  Although imcc has gotten the attention of our developers, the GSoC project's schedule shouldn't make any assumptions as to whether imcc will improve.
+This page exists to help plan out soh_cah_toa's GSoC project.  Unfortunately, it turns out to depend heavily on parts of IMCC which were substantially more broken than anyone realized.  Although IMCC has gotten the attention of our developers, the GSoC project's schedule shouldn't make any assumptions as to whether IMCC will improve.
 
-My (cotto) plan is to rework hbdb's schedule so that it can be a maximally useful debugger by the end of GSoC within the limitations of what imcc can provide.  The first step is to break the original schedule into a list of discrete features and to divide those features into three groups: those that are completed, those that depend on imcc's broken line number annotations and those that don't.  From there, we can work out a new schedule that will show measurable progress and be completable while avoiding some of the more egregious landmines provided by imcc.
+My (cotto) plan is to rework HBDB's schedule so that it can be a maximally useful debugger by the end of GSoC within the limitations of what IMCC can provide.  The first step is to break the original schedule into a list of discrete features and to divide those features into five groups: those that are completed (with or without tests), those that depend on IMCC's broken line number annotations, those that don't, and those that may not be possible due to time constraints.  From there, we can work out a new schedule that will show measurable progress and be completable while avoiding some of the more egregious landmines provided by IMCC.
 
-Anything listed with a '?' means that the likelihood of making it into HBDB by the end of the summer is slim.
+Completed with tests:
+ * Help
 
-FEATURES:
- *  read HLL annotations
- *  read data from debug segment
- * ? code instrumentation (steal from parrot-instrument)
- * ? code introspection (steal from parrot-instrument)
- *  add debugee interactively with a gdb-like 'file' command
- *  enable/disable breakpoints
- *  breakpoints (line)
- *  breakpoints (function)
- *  watchpoints (registers)
- * ? reversible debugging
- *  execute until the next annotation change
- *  backtrace
- *  bytecode disassembly
- * ? debugger scripting
- * ? repl
- *  trace open file handles (including children)
- * ? dynamic memory analysis (check for uninitialized values)
- * ? dynamic memory analysis (destruction-triggered watchpoints)
- *  print internal debugger state info
- *  start/continue execution
- *  single-step execution
- *  print registers
- *  help
- *  source listing
+Completed without tests:
+ * Backtrace
+ * Breakpoints (PC)
+ * Bytecode disassembly
+ * Enable/disable breakpoints
+ * Single-step execution
+ * Source listing
+ * Start/continue execution
+
+Dependent on IMCC cleanups:
+ * Breakpoints (line)
+
+Not dependent on IMCC cleanups:
+ * Add debugee interactively with a gdb-like 'file' command
+ * Breakpoints (function)
+ * Execute until the next annotation change
+ * Print registers
+ * Read HLL annotations
+ * Read data from debug segment
+ * Trace open file handles (including children)
+ * Watchpoints (registers)
+
+May not be possible before end of summer:
+ * Code instrumentation (steal from parrot-instrument)
+ * Code introspection (steal from parrot-instrument)
+ * Debugger scripting
+ * Dynamic memory analysis (check for uninitialized values)
+ * Dynamic memory analysis (destruction-triggered watchpoints)
+ * REPL
+ * Reversible debugging