[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Thematic Crash in ImagesElements
From: |
Riccardo Mottola |
Subject: |
Re: Thematic Crash in ImagesElements |
Date: |
Sun, 29 Nov 2020 00:29:27 +0100 |
User-agent: |
GNUMail (Version 1.3.0) |
Hi,
On 2020-11-28 00:29:56 +0100 Riccardo Mottola <riccardo.mottola@libero.it>
wrote:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xb98e1bde in objc_msg_lookup () from /usr/lib/libobjc.so.4
> (gdb)
> (gdb) bt
> #0 0xb98e1bde in objc_msg_lookup () from /usr/lib/libobjc.so.4
> #1 0x08055401 in -[ImagesView refreshCells] (self=<optimized out>,
> _cmd=0x8058f6e <-[ImageElement initWithView:owner:]+10162>) at
> ImageElement.m:354
> #2 0xb57a3a10 in ?? ()
>
>
> I see nothing trivial there. Printing out ImageElement makes the debugger
> crash (but the stack is corrupted...)
I am unable to reproduce this issue on Linux/amd64 gcc, however I did try
running in Valgrind and nothing suspicious came from the memory checker.
I don't have valgrind on NetBSD, but if most of the codepath executed is the
same (including opening the same) it could have been of interest.
Riccardo