Created attachment 204458 [details] Screenshot of error. Hi. I don't know where to post this to request some help so thought I'd add here. Please feel free to delete and email me if that is better. I've followed the instructions on https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg in order to get some debug info for a crash on Win11 Home 25H2 and Libreoffice 25.8.3 but the WinDbg will not attach to a Process or Executable. I get a Win32 error 0n50 ... which in the typical Windows fashion is completely useless. "The request is not supported". The full screenshot of the error is shown in the attached screenshot. As I followed the instructions and had no issues until I tried to start debugging, I'm assuming, rightly or wrongly, that there is something missing in the instructions (or I missed something but still managed to get everything installed). Any suggestions appreciated. Thanks.
Shows you are launching the 32bit instance of the WinDbg kit. You need to use the 64bit WinDbg instance "Debugging tools for Windows (x64)". LibreOffice is no longer built 32 bit. Ignore the TB39 symbols path, that Tinderbox has been defunct for some time. Also there are no longer project maintained symbols built for the nightly dev builds. You'd have to fully install Visual Studio and git pull the full source to build your own symbol libraries. But you can debug with symbols against a TDF release build, the symbols are obtained from: SRV*https://dev-downloads.libreoffice.org/symstore/symbols So on my nVidia dGPU equipped daily driver I use the following symbol path when debugging a process dump or an attached soffice.bin process. CACHE*C:\symbols64;SRV*https://dev-downloads.libreoffice.org/symstore/symbols;SRV*https://msdl.microsoft.com/download/symbols;SRV*https://driver-symbols.nvidia.com/ @Ilmari, time to rework the Wiki page?
Thanks for the suggestions. I'll have to figure out how to get/find/install this 64 bit WinDbg. I figured I did that so somewhat surprised that a 32 bit got installed. "Lots of swear words regarding Windows". I've never compiled anything on Windows and that's a skill I'm not particularly interested in learning. Is this "symbol" a requirement to get some useful output regarding the crashes? If yes, I'll try to figure that out over Christmas.
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
Hi again. I've tried twice to install the x64 version but it appears to always install x86. I'm giving up for the moment. I will try to recreate the crash that I'm getting in 25.8.3 so it can be reproduced. Unfortunately I haven't been able to get a specific set of steps other than it happens multiple times per day.