* Lazarus (rev 24492 ) compile with FPC trunc (rev 15110)
* Both (lazarus / RTL) compiled with -gw -godwarfsets
* gdb 6.8.3 or gdb 7.0
* Windows Vista 32 Bit
Trying to set a breakpoint to lazarus\ide\project.pp line 2121 (first executable line of function
TUnitInfo.EditorInfoWithEditorComponent(AEditor:
TSourceEditorInterface): TUnitEditorInfo;)
Causes the error (full listing below):
<-break-insert -f project.pp:2121>
^done,bkpt={number="11",type="breakpoint",disp="keep",enabled="y",addr="0x0000001d",file="project.pp",line="2121",times="0",original-location="project.pp:2121"}
Why would a breakpoit be at 0x0000001d ?
The debugged application becomes frozen after this (but that may be the way Lazarus' debugger implementation reacts to the error. (There is no way to get the app to continue running)
* From Console
[DBGTGT] running,thread-id="all"
[Debugger] Console output: ~"[Switching to Thread 5000.0x998]\n" [Debugger] Notify output: ,id="9"
[Debugger] Log output: &"info program\n"
TGDBMIDebugger.ProcessResult Error: ,msg="Warning:\nCannot insert breakpoint 11.\nError accessing memory address 0x1d: I nput/output error.\n"
* From Lazarus "deboug output" window
<info program>
&"info program\n"
~"\tUsing the running image of child Thread 5000.0x998.\n" ~"Program stopped at 0x779b8b2f.\n"
~"It stopped with signal SIGTRAP, Trace/breakpoint trap.\n" ~"Type \"info stack\" or \"info registers\" for more information.\n" ^done
(gdb)
<-break-insert -f project.pp:2121>
^done,bkpt={number="11",type="breakpoint",disp="keep",enabled="y",addr="0x0000001d",file="project.pp",line="2121",times="0",original-location="project.pp:2121"} (gdb)
<-break-enable 11>
^done
(gdb)
<-exec-continue>
^error,msg="Warning:\nCannot insert breakpoint 11.\nError accessing memory address 0x1d: Input/output error.\n"
(gdb)