<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#c18">Comment # 18</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:serval2412@yahoo.fr" title="Julien Nabet <serval2412@yahoo.fr>"> Julien Nabet</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=125516#c17">comment #17</a>) > (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? > ... > 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? I'll be honest, it's far more cumbersome to build on Windows than on Linux. When installing all prerequisites, you can see building has been thought above all for Linux users (I won't complain, I use Linux at home :-)). However, it's simpler than some years ago when I had given up. The things I don't like: - windbg: you find far less doc to debug than for gdb, putting a break at a specific line isn't intuitive, values of vars are often pointer values not useful values, !analyze -v provide less info than gdb's "bt", etc. - build fail after some updates so sometimes you must type "make <some module>.clean". You don't need to do this on Linux or very rarely! and when you don't know which module fail, you must build from scratch with "make clean && make" Anyway, the advantage is you can add logs by putting std::cerr << "<messages> \n"; (with #include <iostream>) and display values of vars, you can test some patches proposed by devs, you can disable some blocks, etc. Now if you're not a programmer, perhaps it won't worth it for you. You decide! :-)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>