Thank you for your help on this. I am building the debug now, not sure if this helps in any way but it appears that nearly all points of failure start with this line:
XTextFieldsSupplier xTextFieldsSupplier = (XTextFieldsSupplier)UnoRuntime.queryInterface(XTextFieldsSupplier.class, textDocument.getXTextDocument()); XEnumerationAccess xEnumerationAccess = xTextFieldsSupplier.getTextFields(); This seems to either result in the freeze or reset connection. I will post more once the debug build is completed . Thanks On Wed, 2011-06-29 at 11:17 +0100, Caolán McNamara wrote: > On Tue, 2011-06-28 at 14:37 +0100, Stuart Ledwich (Hotmail) wrote: > > Thank you for the swift response. I think it sounds like good idea to > > debug libre office to find out exactly where its failing. Do you know > > if there is any blogs/wiki/documentation to help me get started with > > that .Thanks > > This is windows, so not my primary platform, but IIRC "attach to > process" in one of the MSVisual Studio menus will do the right thing, > just looks for soffice in the list. > > If it is crashing on the server side you may have to build your own > LibreOffice from source and rebuild the lib in which it crashes with > debugging symbols, e.g. > http://wiki.documentfoundation.org/Development/Native_Build#Partial_debug_build > to get something more useful out of it. > > C. > > _______________________________________________ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice > _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
