Debugger stopped tracing
lazarus / 12-Debugger

----------------------------------------------------------------------
daringly · 2016-10-19 16:15

For months I have used the Lazarus debugger with no problems. Today,
it stopped, amd I am baffled. I have read most of the threads I can
find on it, and don't see any obvious causes of this.

I can compile, and run a program with F9. If I try F7 or F8 to step,
nothing happens (but F9 will still work after trying f7/F8).

To isolate the issue, I went with the shortest program I could try:

program test1;

begin
  writeln('hello world');
  readln;

end. 

Any suggestions on getting Step to work in debug?

----------------------------------------------------------------------
howardpc · 2016-10-19 16:22

Double check that in your project options you have checked "Generate
debugging info for GDB", that you don't have any optimizations, and
that there is no smartlinking, and that gdb is in your OS Path.

----------------------------------------------------------------------
molly · 2016-10-19 16:26

In addition to what howardpc wrote and perhaps a stupid remark, have
you actually set a breakpoint ? Stepping into a program without so
displays the assembler window (which might be hidden for you).

----------------------------------------------------------------------
wp · 2016-10-19 16:36

Some time ago I switched to gdb v7.9 and sporadically saw these issues
as well. Then I returned to the gdb version that comes with the Laz3.0
installation (I don't know the version number) and everything is fine
again.

----------------------------------------------------------------------
daringly · 2016-10-19 16:39

Quote from: howardpc on October 19, 2016, 06:22:59 pmDouble check that
in your project options you have checked "Generate debugging info for
GDB", that you don't have any optimizations, and that there is no
smartlinking, and that gdb is in your OS Path.

"Generate debugging info for DGB" is still checked."
The default was optimization 1, and I tried 0 as well.
Smart linkable is not checked.
The gdb path is unchanged:
$(LazarusDir)\mingw\$(TargetCPU)-$(TargetOS)\bin\gdb.exe

----------------------------------------------------------------------
daringly · 2016-10-19 16:47

Quote from: wp on October 19, 2016, 06:36:23 pmSome time ago I
switched to gdb v7.9 and sporadically saw these issues as well. Then I
returned to the gdb version that comes with the Laz3.0 installation (I
don't know the version number) and everything is fine again.

My version of gdb is 7.3.50, which was included in the 2016 Lazarus
download.

----------------------------------------------------------------------
Martin_fr · 2016-10-19 17:51

first of all: windows ??
which version of windows? 64 or 32 bits?

Lazarus 32/64 bits?

Then do you have an antivirus? sometimes they cause issues. If you can
try to temp disable it, or put lazarus, gdb and your newly compiled
project on the exception list.

----------------------------------
You say F7/F8 do not work....

Unless your app is a console app, you need to start with F9 and reach
a breakpoint first (F7/F8 would (if anything) take you somewhere into
LCL or RTL....)

Next, if you set a breakpoint, and then run with F9, does the
breakpoint stay in its red color, or does it get another color
(orange-ish)?

-----------------------------------
You can try to switch between stabs and dwarf (project options / debug
info / their is a dropdown)

If nothing helps, the provide a logfile
http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#Log_info_for_debu
g_session

----------------------------------------------------------------------
daringly · 2016-10-20 14:12

Windows 7, 64-bit.
Lazarus 1.6, fpc 3.0.0, x86_64-win64-win32/win64

I am using eset.

----------------------------------------------------------------------
-User- · 2020-03-20 13:07

Quote from: daringly on October 19, 2016, 06:15:23 pmI can compile,
and run a program with F9. If I try F7 or F8 to step, nothing happens
(but F9 will still work after trying f7/F8).I have had the same
problem. Version 7.12 of gdb.exe by Equation Solution works without
such a trouble.
http://www.equation.com/servlet/equation.cmd?fa=gdb

i'd say, problem solved.