View Single Post
Old 12-13-2022, 12:06 PM   #12
svkytbsld
Enthusiast
svkytbsld is a marvel to beholdsvkytbsld is a marvel to beholdsvkytbsld is a marvel to beholdsvkytbsld is a marvel to beholdsvkytbsld is a marvel to beholdsvkytbsld is a marvel to beholdsvkytbsld is a marvel to beholdsvkytbsld is a marvel to beholdsvkytbsld is a marvel to beholdsvkytbsld is a marvel to beholdsvkytbsld is a marvel to behold
 
Posts: 30
Karma: 11674
Join Date: Nov 2021
Device: Kobo Libra 2
Quote:
Originally Posted by NullNix View Post
SIGABRT means "abort() was called" which almost always means a call to assert() failed. Nothing to do with memory management at all: you're probably thinking of SIGSEGV or SIGBUS.

Running a debugger on it should give you a possibly-useful stack backtrace at assertion-failure time. There may also be something printed on stderr.
I don't know what a debugging is.
svkytbsld is offline   Reply With Quote