Debug Lazarus 1.0 RC2 on AMD64 LINUX
lazarus / 12-Debugger

----------------------------------------------------------------------
tintinux · 2012-08-29 19:37

Hi

After a fresh install, on Ubuntu 12.04, the debugger is defined to
"None"

If I select "gdb" and the path "/usr/bin/gdb", I get an error :

Code: [Select]The GDB command: "info functions FPC_CPUINIT" did not
return any result
It raises also a system error.

Is there something to do, to make it working ?

Thanks

Tintinux

----------------------------------------------------------------------
Martin_fr · 2012-08-29 20:45

What version of GDB?


Please create a log, see here http://wiki.lazarus.freepascal.org/GDB_D
ebugger_Tips#Log_info_for_debug_session

lazarus --debug-log=/path/to/yourfiles/laz.log  --debug-enable=DBG_CMD
_ECHO,DBG_STATE,DBG_DATA_MONITORS,DBGMI_QUEUE_DEBUG,DBGMI_TYPE_INFO

----------------------------------------------------------------------
tintinux · 2012-08-31 06:01

Hi

I have attached the log, and think you have the gdb version in it.

May be, in the wiki at http://wiki.lazarus.freepascal.org/GDB_Debugger
_Tips#Log_info_for_debug_session the 0.99 up is wrong and we should
follow the tip for 1.0 and next...

Regards

----------------------------------------------------------------------
Martin_fr · 2012-08-31 12:53

Looks like gdb itself crashes.
Is that the original, as it comes with ubuntu?
/build/buildd/gdb-7.4-2012.04

There are various thinks you can try:
1) Definetly make sure you do NOT use smartlinking
2) do not use higher optimization (only -O1 is ok)
  dwarf with
3) try (on the project options / linking tab

If that does not you need anothr gdb version (7.5 is not yet fully
supported).

--------
This issue is not related to the lazarus itself. except for maybe the
defaults for some options.

The synbols are written by fpc and the linker ( ld ) that comes with
your ubunto.
they are either stabbs or dwarf.
gdb reads them.

I your case gdb crashes when it reads then (well most probably that is
where your gdb crashed)

fpc 2.6.0 which comes with Lazarus 1.0, already was used by 0.9.30.4.
so that did not chak=nge either. unless you upgraded from something
older

----------------------------------------------------------------------
pch · 2012-09-07 13:00

I have the same problem (gdb internal error in info functions
FPC_CPUINIT) on Ubuntu 12.04 after installing Lazarus 1.0, it used to
work fine with 0.9.30.4, same fpc version 2.6.0.

For me this is solved by setting  InternalStartBreak = gdsbMain in the
debugger options.

----------------------------------------------------------------------
Martin_fr · 2012-09-07 13:32

Very strange. But possible.

Lazarus 1.0 sets a different set of breakpoints at startup than
0.9.30.x did. (And this set depends on InternalStartBreak)

Then later Lazarus (0.9.30.x and 1.0) call
Code: [Select]  info functions FPC_CPUINITThat has no obvious
relevance to the breakpoints before. (Does not set or modify, nor is
documented to depend on any breakpoint)


If all the info collected sofar is correct, then I can only conclude,
that setting one of the breakpoints modifies some internal state
(probably symbol cache) in such a way, that a later command fails.

Very scary. I can only conclude that 7.4 is not safe to use. 
And IIRC yes 7.4 introduced some other errors around calculating the
line for a breakpoint. (Which so long as gdb does not crash the IDE
works around)

Some of this (I do not know for sure) may be fixed in 7.5.
BUT 7.5 appears to have changes that the IDE does not understand.
Therefore watches may display wrong, if 7.5 is used.

Recommendation is to use 7.3

----------------------------------------------------------------------
tintinux · 2012-10-20 17:32

Hi

Someone knows how I can downgrade to 7.3 in Ubuntu 12.04 LTS ?

Thanks.