https://bugs.kde.org/show_bug.cgi?id=459520
--- Comment #7 from Christoph Cullmann ---
void QTextBlock::setUserData(QTextBlockUserData *data)
{
if (!p || !n)
return;
const QTextBlockData *b = p->blockMap().fragment(n);
if (data != b->userData)
delete b->userData;
https://bugs.kde.org/show_bug.cgi?id=459520
Christoph Cullmann changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/util
https://bugs.kde.org/show_bug.cgi?id=459520
--- Comment #5 from Christoph Cullmann ---
Good hint!
But just the same backtrace:
But ok, I see
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f7cfe89ffa8 in QTextBlock::setUserData(QTextBlockUserData*) () from
/nix/store
https://bugs.kde.org/show_bug.cgi?id=459520
--- Comment #4 from Eric Armbruster ---
You can still retrieve it using the Crashed Process Viewer (or coredumpctl list
+ debug), but I guess it's on your work machine.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459520
Christoph Cullmann changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=459520
--- Comment #3 from Christoph Cullmann ---
My fix was not sufficient, but I missed to get a backtrace for my crash today.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459520
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #2 from Chris
https://bugs.kde.org/show_bug.cgi?id=459520
--- Comment #1 from Christoph Cullmann ---
Git commit 20c8b60eaab7d666eb079363111a93f0c252ff1c by Christoph Cullmann.
Committed on 22/09/2022 at 19:09.
Pushed by cullmann into branch 'master'.
avoid to use previous block that is not there
same logic a
https://bugs.kde.org/show_bug.cgi?id=459520
Bug Janitor Service changed:
What|Removed |Added
Severity|normal |crash
--
You are receiving this mail bec
