Lazarus
Using the Lazarus IDE => Debugger => Topic started by: AlexTP on October 19, 2020, 10:24:37 pm
-
Distro: GhostBSD
Lazarus r64000.
"which gdb" gives none. "gdb" cannot be run.
Lazarus default path for gdb in dialog: /usr/libexec/gdb.
On debug attempt - IDE error "oops, debugger entered the error state".
Why not to detect missing gdb??
-
After I installed gdb, set its path in IDE (its different path), all works.
-
gdb is included in FreeBSD 12 base - I guess the GhostBSD maintainers omitted it for some reason (possibly because it is a rather old gdb version).
-
Yes, and we must DETECT it, not use some bad fixed path.
It was installed to /usr/local.... (don't remember)
-
Yes, and we must DETECT it, not use some bad fixed path.
It was installed to /usr/local.... (don't remember)
If it was installed to /usr/local then it is not the gdb which is distributed with the base system but a third party installation of gdb. The base system gdb is installed is /usr/libexec.
-
Yes, and Laz must use this 3rd party installation. After DETECT. I set its path in the IDE options and debugging begins to work
-
FreeBSD is supported, GhostBSD is not.
-
We must fix this. Its a bug.
-
We must fix this. Its a bug.
No, it's not.
As trev said: FreeBSD<>GhostBSD
-
At least if the full path is incorrect, we need some simpler error msg. Not "oops, debugger entered the error state".
-
Note that the system level GDB (version)is conservatively chosen to debug the kernel. It is not necessarily the best GDB( version) for lazarus