KiCad loads symbols dynamically on runtime. So Gdb may not see them until
KiCad starts running.
Setting breakpoints works for me if I reply "y" to the "Make breakpoint
pending on future shared library load? (y or [n])" prompt when the source
file is not found. Gdb should also be able to find the
Thanks Jon. I tried that and in that case gdb launched kicad, but it couldn't
find the source file to set a breakpoint. If someone can give me an example of
setting the breakpoint that would be great. I tried relative path and full
path, but still couldn't set the breakpoint in
gdb ./kicad/kicad is starting KiCad from the build directory.
This isn't a fully-supported way of debugging KiCad, but if you want to do
this, you must set the environment variable
KICAD_RUN_FROM_BUILD_DIR=1
Alternatively, since you are running `make install` above, you can use gdb
to debug
Hello All,
Sorry for the long mail.
I'm trying to debug one of my changes using gdb and I've run into a
roadblock.
This is what I did so far,
>> Built KiCAD using following commands
cmake -DCMAKE_BUILD_TYPE=Debug
-G "MSYS Makefiles"
-DCMAKE_PREFIX_PATH=/mingw64
Hello Jon,
Am 06.07.21 um 21:45 schrieb Jon Evans:
> Hi Carsten,
>
> I was reminded of this thread because of this forum post:
> https://forum.kicad.info/t/how-install-kicad-6-x-on-debian/30034/4
>
> Is the fact that there is a 6.0.0 tag on experimental also related to
> this issue with
5 matches
Mail list logo
