| commit | 0b6eff6ed4d50393b50af47b0424c82212b65933 | |
| author | Thays Grazia <thaystg@gmail.com> | |
| Tue, 8 Jan 2019 11:47:04 +0000 (8 09:47 -0200) | ||
| committer | GitHub <noreply@github.com> | |
| Tue, 8 Jan 2019 11:47:04 +0000 (8 09:47 -0200) | ||
| tree | 2dac025636d1fefd7d2161adb121fa81fc512e32 | treesnapshot (tar.gz zip) |
| parent | b9e209fc9376f823707b674ea0a734a54b7a7fb4 | commitdiff |
[debugger] Fix test ShouldCorrectlyStepOverOnExitFromArgsAfterStepInMethodParameter (#12114)
The problem was in this line:
ss_nested_with_two_args(ss_nested_arg (), ss_nested_arg ());
The first step_into works correctly entering in the ss_nested_arg method, but the second one doesn't work.
The problem was because this flag MONO_SEQ_POINT_FLAG_NONEMPTY_STACK was set, so the debugger don't consider that it was a possible break.
The solution of the issue was create another flag to identify nested calls and ignore the MONO_SEQ_POINT_FLAG_NONEMPTY_STACK.
2 new tests were added to test other nested calls.
#Fixes 7326
The problem was in this line:
ss_nested_with_two_args(ss_nested_arg (), ss_nested_arg ());
The first step_into works correctly entering in the ss_nested_arg method, but the second one doesn't work.
The problem was because this flag MONO_SEQ_POINT_FLAG_NONEMPTY_STACK was set, so the debugger don't consider that it was a possible break.
The solution of the issue was create another flag to identify nested calls and ignore the MONO_SEQ_POINT_FLAG_NONEMPTY_STACK.
2 new tests were added to test other nested calls.
#Fixes 7326