From 47aa03ce376e194b9a4f3ddc047b148a7c4a7f17 Mon Sep 17 00:00:00 2001 From: John Preston Date: Mon, 16 Jan 2017 13:18:34 +0300 Subject: [PATCH] Logging string in case of crash inside Qt text processing. There are some crash reports from OS X 10.6 and it is the way to find out which string exactly crashes the app in that place. --- Telegram/SourceFiles/ui/text/text_block.cpp | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Telegram/SourceFiles/ui/text/text_block.cpp b/Telegram/SourceFiles/ui/text/text_block.cpp index 65c010f75..b43bb05dd 100644 --- a/Telegram/SourceFiles/ui/text/text_block.cpp +++ b/Telegram/SourceFiles/ui/text/text_block.cpp @@ -330,6 +330,10 @@ TextBlock::TextBlock(const style::font &font, const QString &str, QFixed minResi } QString part = str.mid(_from, length); + + // Attempt to catch a crash in text processing + SignalHandlers::setCrashAnnotationRef("CrashString", &part); + QStackTextEngine engine(part, blockFont->f); engine.itemize(); @@ -340,6 +344,8 @@ TextBlock::TextBlock(const style::font &font, const QString &str, QFixed minResi BlockParser parser(&engine, this, minResizeWidth, _from, part); layout.endLayout(); + + SignalHandlers::clearCrashAnnotationRef("CrashString"); } }