Sign in Join

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

Mailing lists / lazarus / 2014-11

Lazarus 1.2.6 and GDB 7.7

2 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

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

Tony Whyman

Is anyone having much luck with Lazarus 1.2.6 and GDB 7.7 (I'm using Linux Mint 17/Ubuntu 14.4).

As soon as I start using it with anything more than a simple program and still using the default debug settings, the debugger keeps crashing when an exception occurs. Here's a typical error

While executing the command:
"TGDBMIDebuggerInstruction: "-stack-info-depth 33", [ifRequiresThread] Thr=1"
gdb reported:
"&"/build/buildd/gdb-7.7.1/gdb/buildsym.c:746: internal-error: failed internal consistency check\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.""

I am also having problems inspecting class variables - as in the debugger claims the symbol does not exist.

Reply by email

Martin Frb
to Tony Whyman
Tony Whyman wrote 14 lines
Is anyone having much luck with Lazarus 1.2.6 and GDB 7.7 (I'm using Linux Mint 17/Ubuntu 14.4). As soon as I start using it with anything more than a simple program and still using the default debug settings, the debugger keeps crashing when an exception occurs. Here's a typical error While executing the command: "TGDBMIDebuggerInstruction: "-stack-info-depth 33", [ifRequiresThread] Thr=1" gdb reported: "&"/build/buildd/gdb-7.7.1/gdb/buildsym.c:746: internal-error: failed internal consistency check\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.""

From what I observed, since gdb 7.5.9 those assertions get triggered. With older GDB I had not observed issues like this. In many cases those are either caused by:
1) mixing stabs and dwarf (maybe some package has different settings).
2) smart linking (On some platforms debug info remains for removed code)

I am also having problems inspecting class variables - as in the debugger claims the symbol does not exist.

Depends on if and what debug info fpc generates for them.

Reply by email