kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #19827
Assertion trip due to out-of-order dialog close
-
To:
kicad-developers@xxxxxxxxxxxxxxxxxxx
-
From:
Lorenzo Marcantonio <l.marcantonio@xxxxxxxxxxxx>
-
Date:
Wed, 19 Aug 2015 11:50:37 +0200
-
Organization:
Logos Srl
-
User-agent:
Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/24.5 (x86_64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO)
Could be a window manager related issue or just an untested code path;
in yesterday version:
- Open a board and hover on a part
- 'E' for component properties
- Choose 'Change Footprints'
- With the change dialog open, the footprint properties one is still
focusable; so you can close it (ESC, OK or cancel, doesn't seem to
matter)
- Now try to close the change footprints dialog; the window stack is
messed up and an assertion triggers:
ASSERT INFO:
/home/lomarcan/cvswork/kicad-bzr/common/dialog_shim.cpp(525): assert "Assert failure" failed in EndQuasiModal(): either DIALOG_SHIM::EndQuasiModal called twice or ShowQuasiModal wasn't called
BACKTRACE:
[1] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const
[2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[3] wxEvtHandler::SearchDynamicEventTable(wxEvent&)
[4] wxEvtHandler::TryHereOnly(wxEvent&)
[5] wxEvtHandler::ProcessEventLocally(wxEvent&)
[6] wxEvtHandler::ProcessEvent(wxEvent&)
[7] wxEvtHandler::SafelyProcessEvent(wxEvent&)
(cut of the most unhelpful stack trace ever seen... the interesting
stuff probably already happened and queued the close event before
returning)
--
Lorenzo Marcantonio
Logos Srl
Follow ups