- open the attached database document
- open the form therein for editing
- Tools / Macros / Organize Dialogs
- expand the "Form1" node in the macro organizer
=> crash

This issue is separated out of issue 76066, which described a bug how to
actually *create* such a corrupted document. Now while with the fix for issue
76066, document corruption is much less likely, but nonetheless the organizer
should not crash when it encounters a document which is (however) flawed.

fs->ab: There's a SAXParseException thrown in
SfxDialogLibraryContainer::importLibraryElement, which is called from
SfxLibraryContainer::loadLibrary. There's two issues here:

First, of course the BasicTreeListBox implementation must catch exceptions
thrown from loadLibrary.

Second, even if it does, one could provoke a crash on Unix systems: loadLibrary
is declared to allow to throw NoSuchElementException, WrappedTargetException,
and RuntimeException. That means that on systems whose compiler respects the
exception declaration (the windows compiler doesn't, GCC does), this will crash,
since the SAXParseException is not allowed to leave.