@bfo,
Thanks. Familiar with the reference. Unfortunately completely dependent on a
WNT build done with MSVC debug symbols--not the case for our TinderBox
builds. Process Monitor and its stack trace is a workable alternative, but
it is tedious and gets one only to the ball park--especially if there are
Java bindings involved.
So, what I need a bit of help from someone familiar with the crash/recovery
process in LibreOffice, specifically the Windows builds, to identify the
recovery process dll, so I can work backwards from there.
Stuart
--
View this message in context:
http://nabble.documentfoundation.org/Stack-trace-in-Windows-tp4051411p4051804.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.