This is the question I need answered. Windows by default gives the most useless crash report I've ever seen. All I know from that is that the crash point is inside qt but that doesn't help at all with a Qt based application. Worse a lot the documentation I find assumes you are a) debugging a drive and/or b) working with msvc project that you can reproduce the crash in.
---------- Forwarded message --------- From: Nikolai Rogalskii <roga...@gmail.com> Date: Wed, Nov 16, 2022 at 1:05 PM Subject: KDiff3 v 1.9.6 Windows crash To: <reeves...@gmail.com> Hi Michael In 459484 – Crash and Windows SmartScreen warning (kde.org) <https://bugs.kde.org/show_bug.cgi?id=459484> you say that having an actual stacktrace may help. Can you please point me to the instruction how to gather stack trace? I'm OK with building it locally in debug mode if needed, just need an instruction Thanks, Nikolai Rogalskii
