Debugger failed... no blue balls
lazarus / 12-Debugger

----------------------------------------------------------------------
RedOctober · 2025-05-01 15:01

Lazarus 3.4 (rev lazarus_3_4) FPC 3.2.2 x86_64-win64-win32/win64
OS: Windows Server 2016

My Lazarus IDE suddenly quit debugging for me.  No blue balls.  No
stopping on break points.  I have changed nothing.  Maybe I did a typo
or something?  I can't find the problem.  IDE options file is
attached.

Thanks in advance.

----------------------------------------------------------------------
Martin_fr · 2025-05-01 16:04

I didn't spot anything in the xml..

But please check https://wiki.lazarus.freepascal.org/Debugger_Setup

Also
- Check that there is no projectname.dbg file in either the project
dir, or the lib dir or where ever your exe is. (This would be the case
if at any time "external debug info" was enabled.
- Check the size of the exe => if you toggle "generate info for
debugger" on/off, and rebuild, does the exe size change (by at least
several MB)?

Try a clean rebuild. If needed, remove any ppu/o file (that the
compiler generated) by hand.


Does the "pause" button work? If you press it, does the app get paused
and the assemble is displayed?

Does it affect a new app too.
If you create a new empty form, with an "OnFormCreate" event, and a
breakpoint in it?


What debugger backend do you have configured?

Tools => Options => debugger backend.

All at the top of the frame is a toolbar, with a drop down =>the drop
down will show the name of the current debugger. It ends in the
"backend type" which is also shown in the middle of that frame.

If you use the dropdown to toggle between fpdebug and gdb => any
change?

----------------------------------------------------------------------
RedOctober · 2025-05-01 16:17

All good suggestions Martin_fr.  I will look into these. 

As I think about this more, I remember I DID spark the computer with a
massive static discharge a few hours ago.  The monitor and keyboard
(backlit) went blank for a sec, then came back.  I think this might be
the cause.  Maybe I blew up some memory.  Debug works intermittently. 
I may just do a reboot and see if that fixes this problem.

I do have a de-spark bare metal screw head beside my keyboard that I
usually remember to use, but I forgot this one time as I was in a
hurry.  dam.