Happy to cobble together a couple of clean Win7sp1 systems (32bit, 64bit)
with JRE 1.7.4, Java Access Bridge 2.0.2, NVDA 2012.1 and LibreOffice
3.5.4rc2 to capture the faults.
But for posting "stack- trace" what would folks prefer (be able to use) to
efficiently pin down the issue under Windows, JRE or the JAB?
A Windows Sysinternals Process Monitor log during crash would be my starting
point.
But I could load MinGW for gcc/gdb, or Visual Studio 2008 (or 2005) and
appropriate debug symbols if someone points me to them and lets me know what
they need captured and of any configuration weirdness.
Also, could load Dr. Memory and work with one of the
/win32-debug/libreoffice-3-5 installer packages if that is preferred,
although the 3.5.4rc1 dev version is not yet posted.
Stuart
--
View this message in context:
http://nabble.documentfoundation.org/Bug-46114-Java-Access-Bridge-no-longer-works-tp3986431p3986543.html
Sent from the Dev mailing list archive at Nabble.com.
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.