Your message dated Mon, 2 Jun 2025 22:36:47 +0200
with message-id <ad4lx-ik2a063...@x1.cruise.homelinux.net>
and subject line Re: Bug#1106272: kicad-cli segfault on processing schematic
has caused the Debian Bug report #1106272,
regarding kicad-cli segfault on processing schematic
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1106272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kicad
Version: 9.0.1+dfsg-1~bpo12+1
Severity: important
X-Debbugs-Cc: b.spran...@linutronix.de
Dear Maintainer,
kicad-cli segfault on processing a schematic.
1) Clone project:
$ git clone https://github.com/eurovibes/akkupack-ng.git
2) Change to project and configure core dump
$ cd akkupack-ng
$ ulimit -c unlimited
3) Try to export schematic
$ kicad-cli sch export pdf akkupack-ng.kicad_sch
---> Core dump is written
4) Show core dump
$ gdb /usr/bin/kicad-cli core
GNU gdb (Debian 13.1-3) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kicad-cli...
(No debugging symbols found in /usr/bin/kicad-cli)
[New LWP 5380]
[New LWP 5381]
[New LWP 5382]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `kicad-cli sch export pdf akkupack-ng.kicad_sch'.
--Type <RET> for more, q to quit, c to continue without paging--
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f138d8b7efa in __GI___libc_free (mem=0x9) at ./malloc/malloc.c:3362
3362 ./malloc/malloc.c: Datei oder Verzeichnis nicht gefunden.
[Current thread is 1 (Thread 0x7f13897b0d40 (LWP 5380))]
(gdb) bt
#0 0x00007f138d8b7efa in __GI___libc_free (mem=0x9) at ./malloc/malloc.c:3362
#1 0x00007f138769d378 in ?? () from /usr/bin/_eeschema.kiface
#2 0x00007f1387765f08 in ?? () from /usr/bin/_eeschema.kiface
#3 0x00007f138771e84b in ?? () from /usr/bin/_eeschema.kiface
#4 0x00007f1387707fc6 in ?? () from /usr/bin/_eeschema.kiface
#5 0x00007f13875c5ece in ?? () from /usr/bin/_eeschema.kiface
#6 0x00007f138e0a3f77 in JOB_DISPATCHER::RunJob(JOB*, REPORTER*) ()
from /lib/x86_64-linux-gnu/libkicommon.so.9.0.1
#7 0x000055940a533b8d in ?? ()
#8 0x000055940a4b7d4b in ?? ()
#9 0x000055940a4c77a2 in ?? ()
#10 0x00007f138eb1fec7 in wxEntry(int&, wchar_t**) ()
from /lib/x86_64-linux-gnu/libwx_baseu-3.2.so.0
#11 0x000055940a4b2b18 in ?? ()
#12 0x00007f138d84624a in __libc_start_call_main (
main=main@entry=0x55940a4b2af0, argc=argc@entry=5,
argv=argv@entry=0x7ffe1e5ae0f8)
at ../sysdeps/nptl/libc_start_call_main.h:58
#13 0x00007f138d846305 in __libc_start_main_impl (main=0x55940a4b2af0, argc=5,
argv=0x7ffe1e5ae0f8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7ffe1e5ae0e8)
at ../csu/libc-start.c:360
#14 0x000055940a4b5441 in ?? ()
(gdb) quit
The Problem also occured in 9.0.1+dfsg-1 and is solved in 9.0.2+dfsg-1.
Regards
Benedikt Spranger
-- System Information:
Debian Release: 12.11
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-35-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
LSM: AppArmor: enabled
Versions of packages kicad depends on:
ii libc6 2.36-9+deb12u10
ii libcairo2 1.16.0-7
ii libcurl4 7.88.1-10+deb12u12
ii libfontconfig1 2.14.1-4
ii libfreetype6 2.12.1+dfsg-5+deb12u4
ii libgcc-s1 12.2.0-14+deb12u1
ii libgit2-1.5 1.5.1+ds-1+deb12u1
ii libgl1 1.6.0-1
ii libglew2.2 2.2.0-4+b1
ii libglib2.0-0 2.74.6-2+deb12u6
ii libglu1-mesa [libglu1] 9.0.2-1.1
ii libgtk-3-0 3.24.38-2~deb12u3
ii libharfbuzz0b 6.0.0+dfsg-3
ii libngspice0 39.3+ds-1
ii libnng1 1.5.2-2
ii libocct-data-exchange-7.6 7.6.3+dfsg1-7
ii libocct-foundation-7.6 7.6.3+dfsg1-7
ii libocct-modeling-algorithms-7.6 7.6.3+dfsg1-7
ii libocct-modeling-data-7.6 7.6.3+dfsg1-7
ii libocct-ocaf-7.6 7.6.3+dfsg1-7
ii libodbc2 2.3.11-2+deb12u1
ii libprotobuf32 3.21.12-3
ii libpython3.11 3.11.2-6+deb12u6
ii libsecret-1-0 0.20.5-3
ii libstdc++6 12.2.0-14+deb12u1
ii libwxbase3.2-1 3.2.2+dfsg-2
ii libwxgtk-gl3.2-1 3.2.2+dfsg-2
ii libwxgtk3.2-1 3.2.2+dfsg-2
ii libzstd1 1.5.4+dfsg2-5
ii python3 3.11.2-1+b1
ii python3-wxgtk4.0 4.2.0+dfsg-3
ii zlib1g 1:1.2.13.dfsg-1
Versions of packages kicad recommends:
ii kicad-demos 9.0.1+dfsg-1~bpo12+1
ii kicad-libraries 9.0.1+dfsg-1~bpo12+1
ii xsltproc 1.1.35-1+deb12u1
Versions of packages kicad suggests:
pn extra-xdg-menus <none>
pn kicad-doc-ca | kicad-doc-de | kicad-doc-en | kicad-doc-es | kicad-d <none>
oc-fr | kicad-doc-id | kicad-doc-it | kicad-doc-ja | kicad-doc-pl |
kicad-doc-ru | kicad-doc-zh
pn kicad-packages3d <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 9.0.2+dfsg-1~bpo12+1
Hello Benedikt,
Am Thu, May 22, 2025 at 01:13:19PM +0200 schrieb Benedikt Spranger:
> Package: kicad
> Version: 9.0.1+dfsg-1~bpo12+1
> Severity: important
> X-Debbugs-Cc: b.spran...@linutronix.de
this issues should have been closed by the upload of the version
9.0.2+dfsg-1~bpo12+1 which did happen a few days before.
Close the report now manually.
--
Regards
Carsten
--- End Message ---
