On Sun, May 11, 2025 at 09:43:55PM +0800, Sadeep Madurange wrote:
> On 2025-05-10 03:29:32, Anthony J. Bentley wrote:
> > Sadeep Madurange writes:
> > > I installed KiCad. When I open a schematic file, and click on "Place
> > > Symbols", KiCad crashes while trying to load footprint libraries. I
> > > see the following error in dmesg:
> > >
> > > ### AML PARSE ERROR (0x279a7): Undefined name:
> > > \\_SB_.PCI0.RP09.PEGP.NVDN
> > > error evaluating: \\_SB_.PCI0.LPCB.EC__._Q26
> > > coredump of kicad(51397), write failed: errno 14
> > 
> > Can you install debug-kicad and gdb, run kicad from egdb, and provide
> > a backtrace?
> 
> I'm not sure if I'm doing this right... I installed debug-kicad, and
> started it. Then ran 'gdb kicad {pid}'. Then I ran 'bt' in gdb. I see
> the following log:
> 
> #0  futex () at /tmp/-:2
> #1  0xe9ecdb68483ec671 in ?? ()
> #2  0x00000fc1b9a94d2a in _rthread_cond_timedwait (
>     cond=0xfc236d30400, mutexp=0xfc149d23500, abs=0x0)
>     at /usr/src/lib/libc/thread/rthread_cond.c:102
> #3  0x00000fc1881ca9d6 in g_cond_wait ()
>    from /usr/local/lib/libglib-2.0.so.4201.13
> #4  0x00000fc1881565e5 in g_async_queue_pop_intern_unlocked ()
>    from /usr/local/lib/libglib-2.0.so.4201.13
> #5  0x00000fc1881564f1 in g_async_queue_pop ()
>    from /usr/local/lib/libglib-2.0.so.4201.13
> #6  0x00000fc19e3b855b in fc_thread_func ()
>    from /usr/local/lib/libpangoft2-1.0.so.3801.3
> #7  0x00000fc1881cb2b7 in g_thread_proxy ()
>    from /usr/local/lib/libglib-2.0.so.4201.13
> #8  0x00000fc17536d502 in _rthread_start (v=Unhandled dwarf expression
> opcode 0xa3
> )
>     at /usr/src/lib/librthread/rthread.c:96
> #9  0x00000fc1b9a129ea in __tfork_thread ()
>     at /usr/src/lib/libc/arch/amd64/sys/tfork_thread.S:87
> #10 0x00000fc1b9a129ea in __tfork_thread ()
>     at /usr/src/lib/libc/arch/amd64/sys/tfork_thread.S:87
> Previous frame identical to this frame (corrupt stack?)
> 
> I haven't used gdb. So, pls let me know the steps to capture the logs
> correctly if the above isn't right.

Better wait for the process to hit the crash before typing 'bt'.

> Also, before I execute bt command, I
> see the following log (after a long list of successful Reading
> symbols...):
> 
> Reading symbols from /usr/libexec/ld.so...Error while reading shared
> library symbols:
> Dwarf Error: wrong version in compilation unit header (is 4, should be
> 2) [in module /usr/libexec/ld.so]
> Reading symbols from
> /usr/local/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader_svg.so...done.
> Loaded symbols for
> /usr/local/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader_svg.so
> Reading symbols from /usr/local/lib/librsvg-2.so.41.1...done.
> Loaded symbols for /usr/local/lib/librsvg-2.so.41.1
> Reading symbols from /usr/local/lib/libxml2.so.21.0...done.
> Loaded symbols for /usr/local/lib/libxml2.so.21.0
> [Switching to thread 184380]
> futex () at /tmp/-:2
> 2       /tmp/-: No such file or directory.
>         in /tmp/-

gdb from base is rarely enough to debug anything complicated on clang
archs, please stay with egdb as suggested by Anthony.

> If I run `egdb kicad`, I see the following logs:
> 
> Reading symbols from kicad...
> Reading symbols from /usr/local/bin/.debug/kicad.dbg...
> (gdb) list
> warning: 578    /usr/obj/ports/kicad-9.0.0/kicad-9.0.0/kicad/kicad.cpp:
> No such file or directory

Which makes sense since you don't have the source code extracted in
that directory on your machine.  Yet, the information from the debug
package should make backtraces etc more useful.

> (gdb) bt
> No stack.

At that point you haven't run the program yet.  Either type 'r' to run
it, or attach to an already running process and run 'c' (continue).

Then you'll be able to reproduce your crash and obtain a backtrace
with 'bt'.

-- 
jca