<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - crash on preview of slide transitions, or in slideshow, when OpenGL rendering enabled Windows 10, intel HD Graphics 620 GPU with 26.20.100.6861 driver" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125516#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - crash on preview of slide transitions, or in slideshow, when OpenGL rendering enabled Windows 10, intel HD Graphics 620 GPU with 26.20.100.6861 driver" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125516">bug 125516</a> from <a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>(In reply to Julien Nabet from <a href="show_bug.cgi?id=125516#c16">comment #16</a>) > V Stuart: do you think it could be possible you build sources by following > <a href="https://wiki.documentfoundation.org/Development/BuildingOnWindows">https://wiki.documentfoundation.org/Development/BuildingOnWindows</a> (with > enable-dbgutil in autogen.input) to add some manual traces in order to debug > this? Maybe, but isn't infra's Jenkins TB77 now spinning out debug builds for 64-bit Windows? Nope! Just checked its not: =-=-= Running ./configure with ´--enable-64-bit --without-junit --without-helppack-integration --enable-extension-integration --enable-scripting-beanshell --enable-scripting-javascript --enable-ext-wiki-publisher --enable-ext-nlpsolver --enable-online-update --enable-breakpad --with-help=html --with-myspell-dicts --with-package-format=msi --enable-mergelibs --with-lang=ALL --with-vendor=The Document Foundation (Jenkins) --disable-dependency-tracking --with-external-tar=/home/tdf/lode/ext_tar --with-ucrt-dir=/home/tdf/ucrt --with-export-validation --srcdir=/home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master --enable-option-checking=fatal´ 50 checking whether to build with additional debug utilities... no 51 checking whether to do a debug build... no 52 checking whether to generate debug information... no =-=-= Working with WinDbg linked with the 64-bit symbols from: SRV*<a href="http://dev-downloads.libreoffice.org/symstore/symbols">http://dev-downloads.libreoffice.org/symstore/symbols</a> SRV*<a href="http://msdl.microsoft.com/download/symbols">http://msdl.microsoft.com/download/symbols</a> I have configured Linux VMs and with git compiled builds over the years, but always reluctant actually build Windows binaries from source. With project symbols, the TB daily seemed enough to not need to get things cobbled together to build on Winodws--I have access to the tools, just not in my skill set to build. Always assumed the only thing I can't do is add additional asserts or break-points. Would my WinDbg backtraces for an issue improve much beyond <a href="http://bugs.documentfoundation.org/attachment.cgi?id=155199" name="attach_155199" title="WinDbg 64 Stack Trace of crash">attachment 155199</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=155199&action=edit" title="WinDbg 64 Stack Trace of crash">[details]</a> or <a href="http://bugs.documentfoundation.org/attachment.cgi?id=155200" name="attach_155200" title="WinDbg 64 analyze exception analysis">attachment 155200</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=155200&action=edit" title="WinDbg 64 analyze exception analysis">[details]</a> if I figure out how to clone the git and link to source?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>