← Back to team overview

kicad-developers team mailing list archive

Assertion trip due to out-of-order dialog close

 

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