Lazarus WIN32_SEH debugging with F8
Original Reporter info from Mantis: nanobit @nanobit
-
Reporter name:
Original Reporter info from Mantis: nanobit @nanobit
- Reporter name:
Description:
I tried newest FPC versions (3.2, trunk), made with dTEST_WIN32_SEH,
and how apps react on an (invalid) operation which causes an OS-exception (AV, divByZero, floating point exception):
The debugger correctly shows error message for the OS-exception, but after the message the continuation differs by key command:
a) stepping further with F8 (or F7) is faulty:
Errors (new AVs, privilege problems, ...) arise in all following operations.
This appears regardless of the type of OS-exception.
b) pressing F9 (to reach next breakpoint if there is any), this works.
In summary, there is a big difference between F8 (failure) and F9 (success).
Mantis conversion info:
- Mantis ID: 34502
- OS: Windows
- OS Build: 10
- Platform: win32
- Version: 2.1 (SVN)