Menu ▾ ▴

#395 Improve the debugger

v1.1.x
closed
Erik Hänel
None
v1.1.2
Change Request
2019-08-19
2018-11-18
Erik Hänel
No

The debugger is currently quite basic. Improve the debugger with the possibility to

  • [x] Jump through the stack trace
  • [x] display local tables (incl. their values)
  • [x] display arguments (incl. their values, if possible)
  • [x] display lines and files in the stack trace
  • [ ] convert linebreaks and tabulators into escaped characters
  • [x] a better guess for the current line number in flow control statements

Furthermore improve the usability (buttons).

Analysis:

This requires many changes under the hood to enable the interaction between the window and the kernel.

Implementation:

  • Implementation: A huge amount of changes were required to implement this change.
  • Revision: [r513]
  • Implementation test: The debugger was used in many possible scenarios

Documentation:

  • ChangesLog: Updated
  • Comments: Changed code sections were commented sufficiently
  • Documentation articles: Not updated
  • Language files: updated

Tests:

This change was tested in productive environment. No deviations detected.

Related

Commit: [r513]

Discussion

  • Erik Hänel

    Erik Hänel - 2018-11-18
    • status: open --> accepted
     

  • Erik Hänel

    Erik Hänel - 2018-11-22
    • Version: Planned --> v1.1.2
     

  • Erik Hänel

    Erik Hänel - 2019-02-23
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -8,3 +8,20 @@

 * a better guess for the current line number in flow control statements

 Furthermore improve the usability (buttons).
+
+###Analysis:
+(*Describe, what's the issue and which changes have to be made*)
+
+###Implementation:
+* Implementation: (*Describe, what you've changed*) 
+* Revision: [rXXX]
+* Implementation test: (*Describe the type of test, which you performed, and if it was successful*)
+
+###Documentation:
+* ChangesLog: (*Have you updated the changes log?*)
+* Comments: (*Have you written comments in the code, which describe your change?*)
+* Documentation articles: (*Have you updated the documentation articles?*)
+* Language files: (*Have you updated the language files?*)
+
+###Tests:
+(*Describe, which tests you performed and their outcome*)
    • status: accepted --> analyzing
     

  • Erik Hänel

    Erik Hänel - 2019-03-26
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,16 +1,16 @@
 The debugger is currently quite basic. Improve the debugger with the possibility to

-* Jump through the stack trace
-* display local tables (incl. their values)
-* display arguments (incl. their values, if possible)
-* display lines and files in the stack trace
-* convert linebreaks and tabulators into escaped characters
-* a better guess for the current line number in flow control statements
+* [ ] Jump through the stack trace
+* [x] display local tables (incl. their values)
+* [ ] display arguments (incl. their values, if possible)
+* [ ] display lines and files in the stack trace
+* [ ] convert linebreaks and tabulators into escaped characters
+* [x] a better guess for the current line number in flow control statements

 Furthermore improve the usability (buttons).

 ###Analysis:
-(*Describe, what's the issue and which changes have to be made*)
+This requires many changes under the hood to enable the interaction between the window and the kernel.

 ###Implementation:

 * Implementation: (*Describe, what you've changed*)
    • status: analyzing --> implementing
     

  • Erik Hänel

    Erik Hänel - 2019-03-30
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -13,15 +13,15 @@
 This requires many changes under the hood to enable the interaction between the window and the kernel.

 ###Implementation:
-* Implementation: (*Describe, what you've changed*) 
-* Revision: [rXXX]
-* Implementation test: (*Describe the type of test, which you performed, and if it was successful*)
+* Implementation: A huge amount of changes were required to implement this change.
+* Revision: [r513]
+* Implementation test: The debugger was used in many possible scenarios 

 ###Documentation:
-* ChangesLog: (*Have you updated the changes log?*)
-* Comments: (*Have you written comments in the code, which describe your change?*)
-* Documentation articles: (*Have you updated the documentation articles?*)
-* Language files: (*Have you updated the language files?*)
+* ChangesLog: Updated
+* Comments: Changed code sections were commented sufficiently
+* Documentation articles: Not updated
+* Language files: updated

 ###Tests:
 (*Describe, which tests you performed and their outcome*)
    • status: implementing --> testing
     

    Related

    Commit: [r513]

  • Erik Hänel

    Erik Hänel - 2019-08-19
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -24,4 +24,4 @@

 * Language files: updated

 ###Tests:
-(*Describe, which tests you performed and their outcome*)
+This change was tested in productive environment. No deviations detected.
    • status: testing --> closed
     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB