https://bugs.kde.org/show_bug.cgi?id=487338
michael <reeves...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #8 from michael <reeves...@gmail.com> ---
For linux you would need to either attach the lldb/gdb debugger to kdiff3 or
locate the coredump from a crash.
Coredumps are not always generated by default on all setup arch does produce
them.
https://lldb.llvm.org/use/map.html Provides reference for running programs
with the debugger attached from the start. The bt command can be used at the
when kdiff3 crash to see where this is happening. lldb is generally the
default on MacOS must linux systems will have gdb by default.
Its understandable that some code can't be published. I'll keep on eye out on
my end case too. KDiff3 itself doesn't directly do much with floating point
but some of the frameworks its built on do.
--
You are receiving this mail because:
You are watching all bug changes.
