On Fri, May 25, 2012 at 12:03 PM, Petr Mladek - pmladek@suse.cz wrote:
but I am not sure if my WinDbg output is any good.
It is probably less informative without the .pdb files. Anyway, I guess
that your are on the right way.
As I wrote earlier I have pdb symbols and source links in the WinDbg
outputs,
but I am concerned about missing FAULTING_SOURCE_LINE and
FAULTING_SOURCE_CODE sections.
If you are lost, just ask on this mailing list. Please, mention there
more details about your system, configure options, and the error message
with some context. Please, do it in separate mail, so we do not solve
too many problems in this thread :-)
Will do as I stuck on those on my way to master...
BTW: I am using sources from
http://download.documentfoundation.org/libreoffice/src/.
You might fine some information in the build_info.txt file that is
available next to the related daily build.
Yes, I checked that, but haven't found why I had errors in my attempts
to do the builds.
Thanks for digging into it.
Well, it is very hard for a newcomer as more informations, settings,
parameters and tips you can get from the mailing lists than from wiki
articles. Hope to edit those a little bit when I succeed.
It is hell of a job to browse a huge number of threads to get this
running...
Best regards.
--
View this message in context:
http://nabble.documentfoundation.org/Re-3-5-3rc1-win32-debug-package-tp3984895p3986052.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.