5.0rc2 (20180606) aborts with segfault



I have rebuilt kicad 5.0rc2 from source (on Debian Buster amd64). Kicad from june 6th 2018 crashes with segmentation fault when I try to open library editor from eeshema.

I have tried to run kican within valgrind and I obtain following error:

==8371== Process terminating with default action of signal 11 (SIGSEGV)
==8371== Access not within mapped region at address 0x2A8
==8371== at 0x1D6625D3: COMPONENT_TREE::COMPONENT_TREE(wxWindow*, SYMBOL_LIB_TABLE*, wxObjectDataPtr<CMP_TREE_MODEL_ADAPTER_BASE>&, COMPONENT_TREE::WIDGETS, wxHtmlWindow*) (in /usr/local/bin/_eeschema.kiface)
==8371== by 0x1D65CAEA: CMP_TREE_PANE::CMP_TREE_PANE(LIB_EDIT_FRAME*, LIB_MANAGER*) (in /usr/local/bin/_eeschema.kiface)
==8371== by 0x1D7388F8: LIB_EDIT_FRAME::LIB_EDIT_FRAME(KIWAY*, wxWindow*) (in /usr/local/bin/_eeschema.kiface)
==8371== by 0x1D6B5462: SCH::IFACE::CreateWindow(wxWindow*, int, KIWAY*, int) (in /usr/local/bin/_eeschema.kiface)
==8371== by 0x1DC5F2: ??? (in /usr/local/bin/kicad)
==8371== by 0x182E27: ??? (in /usr/local/bin/kicad)
==8371== by 0x65F16B9: wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) (in /usr/local/lib/libwx_baseu-3.0.so.0.2.0)
==8371== by 0x65F17C2: wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) (in /usr/local/lib/libwx_baseu-3.0.so.0.2.0)
==8371== by 0x65F1B8A: wxEvtHandler::TryHereOnly(wxEvent&) (in /usr/local/lib/libwx_baseu-3.0.so.0.2.0)
==8371== by 0x1C20B8: ??? (in /usr/local/bin/kicad)
==8371== by 0x65F1982: wxEvtHandler::DoTryChain(wxEvent&) (in /usr/local/lib/libwx_baseu-3.0.so.0.2.0)
==8371== by 0x65F1C74: wxEvtHandler::ProcessEvent(wxEvent&) (in /usr/local/lib/libwx_baseu-3.0.so.0.2.0)

Of course, my 5.0rc2 I have built last week ran as expected.

Best regards,



Bug reports go here: https://bugs.launchpad.net/kicad


I wonder why you reported here because you had already reported it in lauchpad (and it has been fixed) :slight_smile:


It was a mistake. I have in a first time reported bug hereā€¦


No worries. It just was mildly perplexing to see the identical report with earlier time there.


Just for the future: it is ok to report a bug here as well (or ask other users if this is really a bug or just a misunderstanding.)

But if you report it on the bugtracker provide a link to that here. (If you already had a discussion here before reporting it, it might help to link the discussion in the bugreport as the information gathered might help the developers.)


This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.