https://bugs.documentfoundation.org/show_bug.cgi?id=169849
--- Comment #3 from V Stuart Foote <[email protected]> --- Yes using WinDbg with 'symbols' will annotate the debug stack with specifics of the lines of code being executed at the manual break point, assert, or access violation. Essential for narrowing down what is happening, without symbols (or source and symbols when locally build with Visual Studio) the result is more corse. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/choosing-a-32-bit-or-64-bit-debugger-package -- You are receiving this mail because: You are the assignee for the bug.
