Can not debug a non-LCL application without including unit Interfaces
Original Reporter info from Mantis: PascalDragon @PascalDragon
-
Reporter name: Sven Barth
Original Reporter info from Mantis: PascalDragon @PascalDragon
- Reporter name: Sven Barth
Description:
I thought this bug was already reported, but well...
If I debug an application that doesn't use unit Interfaces (and thus does not rely on LCL in any way), I can set breakpoints without problems and they are "hit" if the application is run. But if I do a "step in" or "step over" the debugger jumps to the next breakpoint or the application terminates (gracefully) if it can't find another one.
This behavior persists until I include the LCL as a dependency and add the unit Interfaces to the uses list. Then debugging works as expected.
Note: This bug report is not about "start with terminal application" or "no I/O when debugging".
Steps to reproduce:
The following - simple - program (add LCL as a dependency):
program test;
// Include to "enable" debugging
{uses
Interfaces;}
procedure Test;
begin
Writeln('Hello World'); // output isn't important
end;
begin
Test; // put breakpoint here
Test;
Test; // and here
end.
Without "Interfaces" it breaks at the first and third "Test" but nowhere else no matter if I "step in" or "step over". With "Interfaces" I can step into "Test" and also over the first "Test" to the second.
Mantis conversion info:
- Mantis ID: 17089
- OS: Linux
- OS Build: 2.6.34
- Platform: i386
- Version: 0.9.29 (SVN)
- Fixed in version: 0.9.29 (SVN)
- Fixed in revision: 28162 (#92d5ca64)
- Monitored by: » @martin_frb (Martin Friebe)
- Target version: 0.9.30