Quote:
Originally Posted by mrprobert
Kevin, It's from the released copy of v2.3.0.
Is this what you asked for?
Code:
[0x0] ntdll!NtWaitForMultipleObjects+0x14 0x8a897e46d8 0x7ff940294030
[0x1] KERNELBASE!WaitForMultipleObjectsEx+0xf0 0x8a897e46e0 0x7ff940293f2e
[0x2] KERNELBASE!WaitForMultipleObjects+0xe 0x8a897e49d0 0x7ff941dd1f5a
[0x3] kernel32!WerpReportFaultInternal+0x58a 0x8a897e4a10 0x7ff941dd1996
[0x4] kernel32!WerpReportFault+0xbe 0x8a897e4b30 0x7ff940363699
[0x5] KERNELBASE!UnhandledExceptionFilter+0x3d9 0x8a897e4b70 0x7ff9427d5898
...
[0x2e] Qt6Core!QCoreApplication::exec+0x169 0x8a897ee520 0x7ff7908d75d9
[0x2f] Sigil + 0x575d9!Sigil+0x575d9 0x8a897ee580 0x7ff790bb90c0
[0x30] Sigil + 0x3390c0!Sigil+0x3390c0 0x8a897efc10 0x7ff790bbb312
[0x31] Sigil + 0x33b312!Sigil+0x33b312 0x8a897efca0 0x7ff941d77374
[0x32] kernel32!BaseThreadInitThunk+0x14 0x8a897efce0 0x7ff94277cc91
[0x33] ntdll!RtlUserThreadStart+0x21 0x8a897efd10 0x0
|
Yes, that is the call stack trace.
That bug in 2.3.0 that caused the crash was already fixed in master.
But since the Sigil we ship has been fully stripped of debug symbols none of the Sigil calls in the stack trace can be deciphered.
If you build your own, you can always prevent the symbols from being stripped and then the call stack trace shows you so much more.
Thanks!