Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


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




Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.