Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2011-01

Can someone test, pleease - possible problem with dbg info

3 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Martin

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

Reply by email

Paul Ishenin
to Martin
Martin wrote 22 lines
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

Reply by email

Martin
to Paul Ishenin
Paul Ishenin wrote 27 lines
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

Reply by email