[KDE/Mac] Kate / KDevelop Sprint

[René J.V. Bertin]

Talking about Kate (and KDevelop): I just ran into a crashing bug when printing, on OS X 10.9.4 . I'm unsure if I ever tried to print from either Kate or KDevelop on OS X 10.6.8 but this is rather annoying.

Has anyone seen a backtrace like this before?

(lldb) bt
* thread #1: tid = 0x671ce, 0x00007fff8b08c217 CoreFoundation`CFRelease + 39, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x200000008)
  * frame #0: 0x00007fff8b08c217 CoreFoundation`CFRelease + 39
    frame #1: 0x000000010128118d QtGui`qt_mac_create_imagemask(pixmap=<unavailable>, sr=<unavailable>) + 77 at qpixmap_mac.cpp:1076
    frame #2: 0x000000010139bafb QtGui`qt_mac_draw_pattern(info=0x00000001037bf0e0, c=0x000000010e6eee70) + 907 at qpaintengine_mac.cpp:494
    frame #3: 0x00007fff93e1ca6f CoreGraphics`CGPatternDelegateDrawPattern + 66
    frame #4: 0x0000000108d9f75a libPDFRIP.A.dylib`PDFPatternEmitDefinition + 1299
    frame #5: 0x0000000108d9f9c6 libPDFRIP.A.dylib`emitPatternDefinition + 14
    frame #6: 0x00007fff8b0d1382 CoreFoundation`__CFSetApplyFunction_block_invoke + 18
    frame #7: 0x00007fff8b0b58fc CoreFoundation`CFBasicHashApply + 124
    frame #8: 0x00007fff8b0d133d CoreFoundation`CFSetApplyFunction + 173
    frame #9: 0x0000000108d9f993 libPDFRIP.A.dylib`PDFPatternSetEmitDefinitions + 71
    frame #10: 0x0000000108d95a0c libPDFRIP.A.dylib`emit_page_resources(PDFDocument*) + 59
    frame #11: 0x0000000108d959b0 libPDFRIP.A.dylib`PDFDocumentEndPage + 73
    frame #12: 0x0000000108d94570 libPDFRIP.A.dylib`pdf_EndPage + 17
    frame #13: 0x00007fff8f7e7ea3 PrintCore`pdfSpoolingEndPage(void*, void*) + 345
    frame #14: 0x00007fff8f7df835 PrintCore`PJCEndPage(OpaquePMPrintSession*) + 40
    frame #15: 0x00007fff8f7bd3b6 PrintCore`PMSessionEndPageNoDialog + 80
    frame #16: 0x000000010117f2c7 QtGui`QMacPrintEngine::end() + 103
    frame #17: 0x00000001012d8d0e QtGui`QPainter::end(this=<unavailable>) + 142 at qpainter.cpp:1963
    frame #18: 0x000000010d91f6c9 libkatepartinterfaces.4.dylib`KatePrinter::print(doc=<unavailable>) + 16809 at kateprinter.cpp:669
    frame #19: 0x000000010d792ba8 libkatepartinterfaces.4.dylib`KateDocument::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [inlined] KateDocument::print() + 1992 at katedocument.cpp:1855
    frame #20: 0x000000010d792ba0 libkatepartinterfaces.4.dylib`KateDocument::qt_static_metacall(_o=0x0000000104a87a20, _c=<unavailable>, _id=<unavailable>, _a=0x00007fff5fbfdd60) + 1984 at katedocument.moc:267
    frame #21: 0x00000001027693fd QtCore`QMetaObject::activate(sender=0x000000010e518620, m=<unavailable>, local_signal_index=<unavailable>, argv=<unavailable>) + 1693 at qobject.cpp:3567


I checked, for once it's (sadly) not a simple question of passing a null pointer to CFRelease :-/

R.