Menu ▾ ▴

#114 Starting the debugger inside of a procedure ignores its reporting values

v1.0.x
fixed
Erik Hänel
None
v1.0.9
Bug Fix
2017-05-07
2016-09-18
Erik Hänel
No

Starting the debugger in a procedure ignores the current procedure for the reporting functions of the debugger. (Stacktrace, variables, string are empty)

Analysis:
This can probably be solved by documenting the stacktrace although not needed. For the locals one needs to check, whether the debugger was activated in the last procedure line and pass the relevant data afterwards.

Implementation:
This was simply fixed by always-enabling the protocoling of the stack trace. A fix for the variables is not needed, because the variables are gathered just-in-time.

Documentation:
Not needed - Bug fix.

Tests:
The reporting values are now available. Fix implemented successfully.

Discussion

  • Erik Hänel

    Erik Hänel - 2016-09-18
    • status: open --> postponed
    • Version: v1.0.9 --> Planned
    • Milestone: v1.0.x --> v1.1.x
     

  • Erik Hänel

    Erik Hänel - 2016-10-07
    • Version: Planned --> v1.0.9
    • Milestone: v1.1.x --> v1.0.x
     

  • Erik Hänel

    Erik Hänel - 2017-03-13
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1 +1,9 @@
 Starting the debugger in a procedure ignores the current procedure for the reporting functions of the debugger. (Stacktrace, variables, string are empty)
+
+**Analysis:**
+
+**Implementation:**
+
+**Documentation:**
+
+**Tests:**
    • status: postponed --> analyzing
     

  • Erik Hänel

    Erik Hänel - 2017-03-14
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,6 +1,7 @@
 Starting the debugger in a procedure ignores the current procedure for the reporting functions of the debugger. (Stacktrace, variables, string are empty)

 **Analysis:**
+This can probably be solved by documenting the stacktrace although not needed. For the locals one needs to check, whether the debugger was activated in the last procedure line and pass the relevant data afterwards.

 **Implementation:**
    • status: analyzing --> implementing
     

  • Erik Hänel

    Erik Hänel - 2017-03-15
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -4,7 +4,9 @@
 This can probably be solved by documenting the stacktrace although not needed. For the locals one needs to check, whether the debugger was activated in the last procedure line and pass the relevant data afterwards.

 **Implementation:**
+This was simply fixed by always-enabling the protocoling of the stack trace. A fix for the variables is not needed, because the variables are gathered just-in-time.

 **Documentation:**
+Not needed - Bug fix.

 **Tests:**
    • status: implementing --> testing
     

  • Erik Hänel

    Erik Hänel - 2017-05-07
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -10,3 +10,4 @@
 Not needed - Bug fix.

 **Tests:**
+The reporting values are now available. Fix implemented successfully.
    • status: testing --> fixed
     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB