Download as PDF, PPTX
More Related Content
Similar to Debug Points. Breakpoints, but better!
![ESUG 2009: [Project planning], by Tim Mackinnon](https://cdn.slidesharecdn.com/ss_thumbnails/esug2009-planning-251028124040-b55d3034-thumbnail.jpg?width=640&height=640&fit=bounds)
Debug Points. Breakpoints, but better!
- 1. Steven Costiou Debug Points Breakpoints,but better!
- 2. •Breakpoints • The toolto interrupt executions •Debug Points • A framework to implement breakpoints Vocabulary
- 3. •Breakpoints • The toolto interrupt executions •Debug Points • A framework to implement breakpoints Vocabulary
- 4. •Breakpoints become… • Con fi gurable •Composable • Extensible Debug points (if you need…)
- 5. •Breakpoints become… • Con fi gurable •Composable • Extensible Debug points (if you need…) Better user experience
- 6. •Breakpoints become… • Con fi gurable •Composable • Extensible Debug points (if you need…) Better user experience More precision
- 7. •Breakpoints become… • Con fi gurable •Composable • Extensible Debug points (if you need…) Better user experience More precision Domain-speci fi c breakpoints
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30. DEMOS when does ‘value’ variablechange? and what is the value?
- 31. DEMOS when does ‘value’ variablechange? and what is the value? I only want to know when ‘value’ > 7
- 32.
- 33. DEMOS when are we arrivingin m4 from m3?
- 34. DEMOS when are we arrivingin m4 from m3? break here
- 35. DEMOS when are we arrivingin m4 from m3? break here then step…
- 36. DEMOS when are we arrivingin m4 from m3? break here then step… or break here
- 37. DEMOS however other paths cango through m3!
- 38. DEMOS however other paths cango through m3! I only want this path!
- 39. DEMOS however other paths cango through m3! I only want this path! break here
- 40. DEMOS however other paths cango through m3! I only want this path! break here only if break here fi rst
- 41. Building breakpoints •Why? • Recurringneeds • Problem or domain speci fi c needs • New debugging tools (transfering research)
- 42. Building breakpoints •Why? • Recurringneeds • Problem or domain speci fi c needs • New debugging tools (transfering research) •How? • Subclass and specializes the breakpoint model • Subclass and specializes the breakpoint behavioral model • Build presenters for automatic tool integration
- 43.
- 44.
- 45. Simplified model types of breakpoint whatany breakpoint can do
- 46. Simplified model types of breakpoint whatany breakpoint can do Spec presenters
- 47. DEMO: building areplay point
- 48. DEMO: building areplay point I want to control the value of the condition to deterministically choose which branch to execute
- 49. DEMO: building areplay point operation
- 50. DEMO: building areplay point operation replay point
- 51. DEMO: building areplay point operation replay point replace the operation by a custom value
- 52. DEMO: building areplay point operation replay point replace the operation by a custom value inject the value into the conditional
- 53. DEMO: building areplay point ReplayPoint
- 54. Status •Integrated into Pharo12 • Replaces the breakpoint implementation • Works (it should…)
- 55. Status •Integrated into Pharo12 • Replaces the breakpoint implementation • Works (it should…) •What’s next? • Model improvements • GUI improvements • Archive and remove the old breakpoint model
- 56. Acknowledgments •Main developers • MaxZurbriggen (UHZ) — original idea and implementation • Adrien Vanègue (Inria) — Pharo implementation and integration • Steven Costiou (Inria) — design and integration
- 57. Acknowledgments •Main developers • MaxZurbriggen (UHZ) — original idea and implementation • Adrien Vanègue (Inria) — Pharo implementation and integration • Steven Costiou (Inria) — design and integration •Supervision • Marcus Denker (Inria) • Steven Costiou (Inria) • Alberto Bacchelli (UZH)
- 58.