Menu ▾ ▴

#610 Reset debugger after catched error

v1.1.x
fixed
Erik Hänel
None
v1.1.3
Bug Fix
2021-08-02
2021-07-27
Erik Hänel
No

The debugger displays the error message before it is catched by the test procedure flag. But the debugger is not reset, which results in displaying the same error until a new error occurs although no error is present.

Analysis:

The issue is that the member variable sErrorMessage in the NumeReDebugger class is not cleared before a new breakpoint is reached. A possible solution might be to move the corresponding call to sErrorMessage.clear() into NumeReDebugger::resetBP().

Implementation:

  • Implementation: The actual solution was to add sErrorMessage.clear() at the beginning of NumeReDebugger::showBreakPoint()
  • Revision: [r928]
  • Implementation test: Error messages disappeared as desired.

Documentation:

  • [x] ChangesLog updated
  • [ ] Code changes commented
  • Documentation articles:
    • [ ] corresponding documentation articles updated
    • [ ] new documentation articles created
    • [x] not needed
  • Language files:
    • [ ] corresponding language files updated
    • [x] not needed

Tests:

Tested manually. Error messages disappear at the next "real" breakpoint.

Related

Commit: [r928]

Discussion

  • Erik Hänel

    Erik Hänel - 2021-07-28
    • status: open --> accepted
     

  • Erik Hänel

    Erik Hänel - 2021-07-28
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1 +1,23 @@
 The debugger displays the error message before it is catched by the `test` procedure flag. But the debugger is not reset, which results in displaying the same error until a new error occurs although no error is present.
+
+###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 updated
+* [ ] Code changes commented
+* **Documentation articles:**

+    * [ ] corresponding documentation articles updated
+    * [ ] new documentation articles created
+    * [ ] not needed
+* **Language files:**
+    * [ ] corresponding language files updated
+    * [ ] not needed
+
+###Tests:
+(*Describe, which tests you performed and their outcome*)
    • status: accepted --> analyzing
     

  • Erik Hänel

    Erik Hänel - 2021-07-28
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,7 +1,7 @@
 The debugger displays the error message before it is catched by the `test` procedure flag. But the debugger is not reset, which results in displaying the same error until a new error occurs although no error is present.

 ###Analysis:
-(*Describe, what's the issue and which changes have to be made*)
+The issue is that the member variable `sErrorMessage` in the `NumeReDebugger` class is not cleared before a new breakpoint is reached. A possible solution might be to move the corresponding call to `sErrorMessage.clear()` into `NumeReDebugger::resetBP()`.

 ###Implementation:

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

  • Erik Hänel

    Erik Hänel - 2021-07-28
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -4,20 +4,20 @@
 The issue is that the member variable `sErrorMessage` in the `NumeReDebugger` class is not cleared before a new breakpoint is reached. A possible solution might be to move the corresponding call to `sErrorMessage.clear()` into `NumeReDebugger::resetBP()`.

 ###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: The actual solution was to add `sErrorMessage.clear()` at the beginning of `NumeReDebugger::showBreakPoint()`
+* Revision: [r928]
+* Implementation test: Error messages disappeared as desired.

 ###Documentation:
-* [ ] ChangesLog updated
+* [x] ChangesLog updated

 * [ ] Code changes commented
 * **Documentation articles:**
     * [ ] corresponding documentation articles updated
     * [ ] new documentation articles created
-    * [ ] not needed
+    * [x] not needed
 * **Language files:**
     * [ ] corresponding language files updated
-    * [ ] not needed
+    * [x] not needed

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

    Related

    Commit: [r928]

  • Erik Hänel

    Erik Hänel - 2021-08-02
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -20,4 +20,4 @@

     * [x] not needed

 ###Tests:
-(*Describe, which tests you performed and their outcome*)
+Tested manually. Error messages disappear at the next "real" breakpoint.
    • status: testing --> fixed
     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB