Debugger hangs if program previously aborted with error
Original Reporter info from Mantis: PascalDragon @PascalDragon
-
Reporter name: Sven Barth
Original Reporter info from Mantis: PascalDragon @PascalDragon
- Reporter name: Sven Barth
Description:
This is kinda a follow up of #37861 (closed), though I have not checked whether it behaved this way before the addition of the dialog as well (though it does not happen with 2.0.10).
I have the following main program:
program tdlltest; {$mode objfpc}{$H+} procedure Test; external 'Foobar.dll' name 'Test'; begin Test; end.
The library &LtPos;i>Foobar.dll&LtPos;/i> does not exist, so running it will abort with an error.
Now for the following it doesn't matter if I have the "dialog on error" enabled or not: if I run the program again the IDE will change its title bar to "(Debugging...)", but the stop button won't be enabled and no command line window will appear. The debug output window is empty. Trying to close the IDE will display the "do you want to stop debugging"-dialog and no matter what the IDE won't terminate after the dialog is confirmed. I need to kill it using Task Manager.
Additional information:
This happens with both versions of GDB provided by Lazarus.
It does not happen if the program ran without error.
Mantis conversion info:
- Mantis ID: 37885
- OS: Windows NT
- OS Build: 10
- Build: 63965
- Platform: X86_64
- Version: 2.1 (SVN)
- Fixed in version: 2.2
- Fixed in revision: 63966 (#12b79cfb)
- Target version: 2.2