Le 16/10/11 08:50, jowyta a écrit :
Hi John,
Thanks, Andreas, this is helpful and moves us in the right direction.
This bug, https://bugs.freedesktop.org/show_bug.cgi?id=35023 has been
marked as not our problem since base runs OK with earlier versions of
OpenJDK. However, I do not think that we know this. The problem could
be as a result of an intended change in Java such as the tightening up
of a variable definition or the closing of a vulnerability. If it is a
Java bug then we need to be in a position to say that our application
does not run properly because OpenJDK does not work in the way that the
Java specifications say it should in the following way...
So, how to we drill down deeper to isolate this problem?
You would probably need someone with a debug build of LibO master branch
who can find some way to analyse the Java stack using gdb or valgrind or
some other reporting tool. From what I gather from past discussions, it
is currently actually quite difficult to do that, but I could be wrong
and things could have moved forward since then.
Alex
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-users] Re: Base slowness and Java update (continued)
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.