https://bugs.kde.org/show_bug.cgi?id=424757
Dmitry Kazakov <dimul...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dimul...@gmail.com
--- Comment #8 from Dmitry Kazakov <dimul...@gmail.com> ---
I cannot reproduce the problem :(
I tried to reproduce the crash by emulating memory corruption, but still
couldn't get the same backtrace. It looks like some pointer gets value
0x0000000100000000, and then one of its members with offset 0x20 is read. But
it is neither (MoveStrokeStrategy*)this, nor
KisStrokeStrategyUndoCommandBased::m_macroCommand. Both of them give different
offsets.
--
You are receiving this mail because:
You are watching all bug changes.
