Trying to upgrade from KiCad 4 to 5 I completely removed KiCad 4 and installed the latest version via backports (using deb http://http.debian.net/debian stretch-backports main contrib non-free
)
First of all, when I start kicad, the window title says: KiCad (6.0.0-rc1-dev-86-g887ee4693)
. Shouldn’t that read something like KiCad (5.x.x)
? Running apt-cache show kicad
returns version 5.0.1+dfsg1-3~bpo9+1
The main interface opens and I’m able to select an existing project, or create a new one. But as soon as I try to use the Schematic Layout editor or the Symbol library editor, Kicad crashes with a segmentation fault. The other options (PCB layout editor, Footprint library editor, etc.) do seem to work (haven’t test extensively but they do open as expected).
Does anyone has any ideas as to what I could try to get this to work?
I’m running Debian 9.6 (Stretch).
uname -a: Linux <hostname> 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux
Below is the result from running valgrind kicad -v
and clicking the Schematic Layout editor.
Memcheck, a memory error detector
Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
Command: kicad -v
Invalid read of size 8
at 0x1B336155: DIALOG_SHIM::DIALOG_SHIM(wxWindow*, int, wxString const&, wxPoint const&, wxSize const&, long, wxString const&) (in /usr/local/bin/_eeschema.kiface)
by 0x1AFACB84: DIALOG_GLOBAL_SYM_LIB_TABLE_CONFIG_BASE::DIALOG_GLOBAL_SYM_LIB_TABLE_CONFIG_BASE(wxWindow*, int, wxString const&, wxPoint const&, wxSize const&, long) (in /usr/local/bin/_eeschema.kiface)
by 0x1AFAA0CD: DIALOG_GLOBAL_SYM_LIB_TABLE_CONFIG::DIALOG_GLOBAL_SYM_LIB_TABLE_CONFIG(wxWindow*) (in /usr/local/bin/_eeschema.kiface)
by 0x1B094FA9: SCH::IFACE::OnKifaceStart(PGM_BASE*, int) (in /usr/local/bin/_eeschema.kiface)
by 0x1E9339: ??? (in /usr/local/bin/kicad)
by 0x1E83BA: ??? (in /usr/local/bin/kicad)
by 0x1888DB: ??? (in /usr/local/bin/kicad)
by 0x188CEA: ??? (in /usr/local/bin/kicad)
by 0x650640D: wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const (in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.2.0)
by 0x668BEA4: wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) (in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.2.0)
by 0x668BF9A: wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) (in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.2.0)
by 0x668C34A: wxEvtHandler::TryHereOnly(wxEvent&) (in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.2.0)
Address 0x58 is not stack'd, malloc'd or (recently) free'd
Process terminating with default action of signal 11 (SIGSEGV)
Access not within mapped region at address 0x58
at 0x1B336155: DIALOG_SHIM::DIALOG_SHIM(wxWindow*, int, wxString const&, wxPoint const&, wxSize const&, long, wxString const&) (in /usr/local/bin/_eeschema.kiface)
by 0x1AFACB84: DIALOG_GLOBAL_SYM_LIB_TABLE_CONFIG_BASE::DIALOG_GLOBAL_SYM_LIB_TABLE_CONFIG_BASE(wxWindow*, int, wxString const&, wxPoint const&, wxSize const&, long) (in /usr/local/bin/_eeschema.kiface)
by 0x1AFAA0CD: DIALOG_GLOBAL_SYM_LIB_TABLE_CONFIG::DIALOG_GLOBAL_SYM_LIB_TABLE_CONFIG(wxWindow*) (in /usr/local/bin/_eeschema.kiface)
by 0x1B094FA9: SCH::IFACE::OnKifaceStart(PGM_BASE*, int) (in /usr/local/bin/_eeschema.kiface)
by 0x1E9339: ??? (in /usr/local/bin/kicad)
by 0x1E83BA: ??? (in /usr/local/bin/kicad)
by 0x1888DB: ??? (in /usr/local/bin/kicad)
by 0x188CEA: ??? (in /usr/local/bin/kicad)
by 0x650640D: wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const (in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.2.0)
by 0x668BEA4: wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) (in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.2.0)
by 0x668BF9A: wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) (in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.2.0)
by 0x668C34A: wxEvtHandler::TryHereOnly(wxEvent&) (in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.2.0)
If you believe this happened as a result of a stack
overflow in your program's main thread (unlikely but
possible), you can try to increase the size of the
main thread stack using the --main-stacksize= flag.
The main thread stack size used in this run was 8388608.
HEAP SUMMARY:
in use at exit: 26,601,321 bytes in 113,571 blocks
total heap usage: 534,647 allocs, 421,076 frees, 97,570,892 bytes allocated
LEAK SUMMARY:
definitely lost: 4,096 bytes in 7 blocks
indirectly lost: 20,355 bytes in 825 blocks
possibly lost: 4,028 bytes in 34 blocks
still reachable: 26,332,250 bytes in 110,839 blocks
of which reachable via heuristic:
length64 : 5,256 bytes in 81 blocks
newarray : 22,720 bytes in 74 blocks
suppressed: 0 bytes in 0 blocks
Rerun with --leak-check=full to see details of leaked memory
For counts of detected and suppressed errors, rerun with: -v
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
[1] 24217 killed valgrind kicad -v