mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-08 07:42:33 +01:00
Code Issues Packages Projects Releases Wiki Activity

create 19.12 branch

Browse Source 
git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@2229 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
jfiat
2019-12-28 20:04:57 +00:00
parent 4e06893808
commit 8ce4fd738c
2943 changed files with 62386 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
documentation/19.12/eiffelstudio/eiffelstudio-reference/debugger/debugging-limitations.wiki Normal file
View File

@@ -0,0 +1,22 @@
[[Property:title|Debugging limitations]]
[[Property:weight|-2]]
[[Property:uuid|4377d765-8664-ee0c-5d5b-e42fd7d172c3]]
==General limitations==
* Watch expression: Agents are not supported (for instance "agent my_function" is not supported").
* You cannot yet create an instance of SPECIAL.
* The debugger is not very helpful when the execution is stopped inside an invariant.
* Wrong assertion tag shown in debugger for precondition violation if violated during an exception rescue, indeed the tag remains the one from the exception
* If you use the "Disable Assertion Handling" functionality when the execution is stopped in a rescue, the effect might be cancelled as soon as the execution exits the rescue's associated feature.
* Evaluating an expression with a catcall might crash the debugger
==Limitations or known bugs for the Classic debugger==
* Evaluating <code>Precursor</code> will produce the current feature's <code>Result</code> (not the precursor)
* If you use any of the previous non supported expressions in a breakpoint condition, since the evaluation is failing the condition will always return True. In such case the debugger will stop.
==Limitations or known bugs for the .Net debugger==
* When stepping through disabled assertions or disabled debug clauses, the debugger may show incorrect current line.
* When stepping through an inspect code, the debugger may show incorrect current line (especially if the inspect is not ordered)
* Under dotnet v2.0, the debugger may have difficulties to fetch the stack values, especially during first chance exception events