fpDebug not goto error line in source code
lazarus / 12-Debugger

----------------------------------------------------------------------
tsknv · 2022-05-26 02:21

Hello.
Project for example  attached.
Click to Button1 occur  exception "Operation not allowed, dataset ...
is not in an edit or insert state."
If use GDB - Lazarus goto to error line in project source code (43:
BufDataset.FieldByName('fld1').Value := '!!!'
If use fpDebug - Lazarus show assembler window and not show error in
pascal source code.
DWARF(-gw3) is enabled in project options
What am I doing wrong?

Lazarus 2.2.2

----------------------------------------------------------------------
Thaddy · 2022-05-26 06:47

Did you enable lineinfo?

----------------------------------------------------------------------
tsknv · 2022-05-26 06:58

option -gl is enabled

----------------------------------------------------------------------
Martin_fr · 2022-05-26 11:07

What does the stack window show?

Also what is the address in the asm window?
And, are there any name in the address window?

----------------------------------------------------------------------
Martin_fr · 2022-05-26 11:29

I had a quick look. Yes there is an issue. Actually I recall, I had
noted that before, its buried somewhere on my todo.
Unfortunately it will take some time to fix...

The stack window should show some info, and you can locate your code
in there.

----------------------------------------------------------------------
tsknv · 2022-05-26 11:41

Screenshot stack and asm the windows attached this message

----------------------------------------------------------------------
tsknv · 2022-05-26 11:58

Quote from: Martin_fr on May 26, 2022, 01:29:22 pm...
Unfortunately it will take some time to fix...
The stack window should show some info, and you can locate your code
in there.

Understood. Thanks you.

----------------------------------------------------------------------
korba812 · 2022-05-26 12:13

It looks like you have fpc packages compiled without debug
information. You need to compile packages (fcl-db in this case) with
debug information enabled.

----------------------------------------------------------------------
Martin_fr · 2022-05-26 13:18

Quote from: korba812 on May 26, 2022, 02:13:14 pmIt looks like you
have fpc packages compiled without debug information. You need to
compile packages (fcl-db in this case) with debug information enabled.
No, he doesn't need. (unless he wants to see the line in fcl-db)

If there is no debug info in fcl-db, then the debugger is supposed to
find the first line that has debug info.
In this case his ButtonClick.

----------------------------------------------------------------------
tsknv · 2022-05-26 13:44

Quote from: korba812 on May 26, 2022, 02:13:14 pmIt looks like you
have fpc packages compiled without debug information. You need to
compile packages (fcl-db in this case) with debug information enabled.
In this example I debug only my project, I don't want to debug
packages.

I change only debuger in Lazarus options and no change any other
options - GDB shows the line in the my project (not in the package,
packages compiled without debug infomation) that caused the exception,
fpDebug does not.

----------------------------------------------------------------------
korba812 · 2022-05-26 14:02

Quote from: Martin_fr on May 26, 2022, 03:18:34 pmNo, he doesn't need.
(unless he wants to see the line in fcl-db)

If there is no debug info in fcl-db, then the debugger is supposed to
find the first line that has debug info.
In this case his ButtonClick.
Ah, ok. Sorry for noise.

----------------------------------------------------------------------
Martin_fr · 2022-05-26 14:03

The problem is that GDB blocks the IDE while it gets stack info.
FpDebug doesn't block the IDE.

But the code (for finding the source line of an exception) does
currently not take that into account. It doesn't wait, for the info.
And so it does nothing when using FpDebug.