Debugger error
lazarus / 12-Debugger

----------------------------------------------------------------------
MaxCuriosus · 2020-03-19 12:59

Code: Text  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i The GDB
command:"info address main"returned the error:",msg="No symbol
\"main\" in current context.""
What did I miss?
(Debian9, Laz2.0.2, FPC3.0.4)

----------------------------------------------------------------------
Martin_fr · 2020-03-19 14:48

You may be able to work around the issue by going to Tools > Options
The Debugger. There you find a "property grid", and in it
"InternalStartBreak" => You may want to try and change it. "gdsbEntry"
or "gdsbAddZero" may work. (In trunk: "gdsbNone")

Background:

When running the app, the IDE must tell gdb where to set breakpoints
(including some internal breaks, that are not set by the user).
Historically that was done when the app reaches the "main" procedure
(after starting the app). For that the IDE sets a break at "main".
The change of the above setting allows the IDE to change the location
at which this work is done ("main" can be used by libraries, which for
some gdb versions caused confusion / but in your case it is different,
as it is absent)

I believe this should be fixed for the next major release :
Revision: 62323
Date: 03 December 2019 23:11:57
DebuggerGdbMI: Improved setting breaks for exception stepping. Detect
some errors, and reduce unnecessary retries

----------------------------------------------------------------------
ccrause · 2020-03-19 15:02

Is the option "Generate debugging info for GDB" enabled (Project
Options - Compiler options - Debugging)?

----------------------------------------------------------------------
MaxCuriosus · 2020-03-20 12:56

Martin_fr,
your workaround suggestion to change the option "InternalStartBreak"
to "gdbsEntry" or "gdbsAddZero" did not work, and I left it to
"gdsbDefault".

ccrause,
The option "Generate debugging info for GDB" wasn't enabled, but
enabling it did not help. However I left it checked as in another
similar but functional project.

I've tried also to rename "unit1" to "main" but to no avail.

Then, in the folder project, I deleted all files and folders that are
normally created at first compile, recompiled, and that solved the
debugger error.