[fpc-devel] Can someone test, pleease - possible problem with dbg info
In lazarus /debugger/test/Gdbmi is a program TestGdbmi If I insert a breakpoint at line 480 (either before start, or during run, then GDB reports : >> TCmdLineDebugger.SendCmdLn "-exec-continue" << TCmdLineDebugger.ReadLn "^error,msg="Warning:\nCannot insert breakpoint 9.\nError accessing memory address 0x18: Input/output error.\n" " TGDBMIDebugger.ProcessResult Error: ,msg="Warning:\nCannot insert breakpoint 9.\nError accessing memory address 0x18: Input/output error.\ n" << TCmdLineDebugger.ReadLn "(gdb) " Can anyone try if they get the same? w32 fpc 2.4.2 lazarus uptodate0/9/31 dwarf -gw Oh, and the problem goes away, if I use the external linker -Xe Martin ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Can someone test, pleease - possible problem with dbg info
15.01.2011 8:38, Martin wrote: In lazarus /debugger/test/Gdbmi is a program TestGdbmi If I insert a breakpoint at line 480 (either before start, or during run, then GDB reports : >> TCmdLineDebugger.SendCmdLn "-exec-continue" << TCmdLineDebugger.ReadLn "^error,msg="Warning:\nCannot insert breakpoint 9.\nError accessing memory address 0x18: Input/output error.\n" " TGDBMIDebugger.ProcessResult Error: ,msg="Warning:\nCannot insert breakpoint 9.\nError accessing memory address 0x18: Input/output error.\ n" << TCmdLineDebugger.ReadLn "(gdb) " Can anyone try if they get the same? w32 fpc 2.4.2 lazarus uptodate0/9/31 dwarf -gw Oh, and the problem goes away, if I use the external linker -Xe You have a known problem. You placed a breakpoint at the location which was striped away by the linker. But debug info for this location is generated and not stripped by the compiler. There is already a bug report regards that. Best regards, Paul Ishenin ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Can someone test, pleease - possible problem with dbg info
On 15/01/2011 01:50, Paul Ishenin wrote: 15.01.2011 8:38, Martin wrote: In lazarus /debugger/test/Gdbmi is a program TestGdbmi If I insert a breakpoint at line 480 (either before start, or during run, then GDB reports : >> TCmdLineDebugger.SendCmdLn "-exec-continue" << TCmdLineDebugger.ReadLn "^error,msg="Warning:\nCannot insert breakpoint 9.\nError accessing memory address 0x18: Input/output error.\n" " TGDBMIDebugger.ProcessResult Error: ,msg="Warning:\nCannot insert breakpoint 9.\nError accessing memory address 0x18: Input/output error.\ n" << TCmdLineDebugger.ReadLn "(gdb) " Can anyone try if they get the same? w32 fpc 2.4.2 lazarus uptodate0/9/31 dwarf -gw Oh, and the problem goes away, if I use the external linker -Xe You have a known problem. You placed a breakpoint at the location which was striped away by the linker. But debug info for this location is generated and not stripped by the compiler. There is already a bug report regards that. ok, because it showed the blue dots for the lines... thanks ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
