https://bugs.kde.org/show_bug.cgi?id=525060
--- Comment #2 from Adrian Damian <[email protected]> --- Created attachment 195662 --> https://bugs.kde.org/attachment.cgi?id=195662&action=edit "kate quit unexpectedly" report #1 (no debug symbols) OK, there was another crash; "kate quit unexpectedly" report attached (most likely, the dialog appeared before too, and I just dismissed it, my bad). When the crash happened, a Kate instance had just been opened via the dock, and what caused the crash was running `kate file.py` from the terminal (but, usually that works fine). The traceback seems to be missing Kate debug symbols, but there's additional info that may be useful: Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x0000000185811990 Termination Reason: Namespace SIGNAL, Code 5, Trace/BPT trap: 5 Terminating Process: exc handler [3534] Application Specific Information: BUG IN CLIENT OF LIBMALLOC: memory corruption of free block Abort Cause 48069361856 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_malloc.dylib 0x185811990 _xzm_xzone_malloc_freelist_outlined + 856 ... 0x189ecb164 -[NSApplication run] + 408 42 libqcocoa.dylib 0x10712161c 0x10710c000 + 87580 43 QtCore 0x10537ab10 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 588 44 QtCore 0x105371514 QCoreApplication::exec() + 228 45 kate 0x1024f122c 0x1024e0000 + 70188 46 dyld 0x18562fe00 start + 6992 Will be back when I have a better traceback. -- You are receiving this mail because: You are watching all bug changes.
