Many crashes can be solved easily just by backtrace. It is usually the only way if developers are not able to reproduce it on their system. The backtrace is almost useless without debugging symbols. Mozilla project has a dedicated server where users could download all the needed stuff easily, see: https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg https://developer.mozilla.org/en/Using_the_Mozilla_symbol_server https://developer.mozilla.org/en/Using_the_Mozilla_source_server https://developer.mozilla.org/en/Debugging_a_minidump There are even hints how to setup such server, see: http://zenit.senecac.on.ca/wiki/index.php/Mozilla_Source_and_Symbol_Server Blog postings, bugs on b.m.o, other resources also worth of checking: http://crashopensource.wordpress.com/2007/09/20/starting-the-project-mozilla-source-and-symbol-server/ https://bugzilla.mozilla.org/show_bug.cgi?id=385792 https://bugzilla.mozilla.org/show_bug.cgi?id=408134 https://bugzilla.mozilla.org/show_bug.cgi?id=419904 https://bugzilla.mozilla.org/show_bug.cgi?id=424240 https://bugzilla.mozilla.org/show_bug.cgi?id=424817 https://bugzilla.mozilla.org/show_bug.cgi?id=428518 http://web.archive.org/web/20071218162257/http://www.jorgon.freeserve.co.uk/Other/pdb.htm Thanks bfo for collecting all the above information.
Additional links: http://zenit.senecac.on.ca/wiki/index.php/Add_Source_Server_Support_for_Mercurial https://bugzilla.mozilla.org/show_bug.cgi?id=440001 http://michaelfcollins3.me/2010/09/integrating-git-and-mercurial-with-source-server/
Last batch: http://michaelfcollins3.me/2010/10/mercurial-and-source-server-take-3 https://bitbucket.org/andriy.c/hgsrcsrv https://github.com/joliver/SourceServer-GitExtensions Good luck to anyone who can take it.
You're working on this right Fridrich ? :-)
There is a test symbol server available on http://dev-builds.libreoffice.org/windows-debug/symbols. It contains symbols for builds whose installers can be found at http://dev-builds.libreoffice.org/windows-debug/msi I am just writing the instructions in wiki how to get a trace with WinDBG. I tried it in a clean virtual machine with WinDBG, Visual Studio 2008 and Visual Studio 2010 and was able to set breakpoints and have them hit.
With that, you should be able to enable the automatic crash reports on Windows again and get some meaningful crash report information.
Great news. Hope this will be refreshed every minor release and added to SI GUI eventually. It will make delivering backtraces for Windows an easier task. BTW: is it possible to put there sources archive to download and make backtraces even more useful for developers?
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility. see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
Starting with 4.2.0rc1 you can get pdb files for debugging the release builds. The symbol server's URL is: http://dev-downloads.libreoffice.org/symstore/symbols For daily debug builds use http://dev-builds.libreoffice.org/daily/master/Win-x86@39/current to get a debug build with the symbols available at: http://dev-builds.libreoffice.org/daily/master/Win-x86@39/symbols
Hi *, And with 4.2.0rc2, the symbol files are also source-indexed, so closing this one as fixed :-) source-fetching command is using powershell command to download from cgit.freedesktop.org (that means Windows XP and Vista users need to install it manually, as I think it is not installed automatically with SP3) - if you have other suggestion that works across windows versions and is a better option, feel free to suggest alternatives. The source-indexing only covers files that are used untouched from the checkout. I.e. created headers or files from the external components that are built as part of LibreOffice are not included.
something has broken with this lately, access to: http://dev-downloads.libreoffice.org/symstore/symbols/ gives a '403 Forbidden' response message
(In reply to comment #10) > something has broken with this lately, access to: > http://dev-downloads.libreoffice.org/symstore/symbols/ > > gives a '403 Forbidden' response message That is normal. Per Christian, and in weeks of practice, the dbghelp.dll will correctly parse the symbols repo. Not intended that you be able to browse the content with a web browse.
Back to FIXED.
Migrating Whiteboard tags to Keywords: (EasyHack DifficultyInteresting SkillInfra TopicDebug TopicWeb) [NinjaEdit]
Remove LibreOffice Dev List from CC on EasyHacks (curtailing excessive email to list) [NinjaEdit]