----------------------------------------------------------------------------------
@MSGID: uYnqz@news.chiark.greenend.org.uk>
2d07ef1a
@REPLY: 1@dont-email.me> 96668888
@REPLYADDR Theo
<theom+news@chiark.greenend.org.uk>
@REPLYTO 2:5075/128 Theo
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
uYnqz@news.chiark.greenend.org.uk>
@RFC-References: 1@dont-email.me>
1@dont-email.me> 1@dont-email.me>
@TZUTC: 0100
@PID: tin/1.8.3-20070201 ("Scotasay") (UNIX)
(Linux/5.10.0-22-amd64 (x86_64))
@TID: FIDOGATE-5.12-ge4e8b94
In comp.sys.raspberry-pi The Natural Philosopher <
tnp@invalid.invalid> wrote:
> both already done. Not closng it was the cause of a memory leak but I
> fixed that a fortnight ago.
>
> I am beginning to wonder if I did more damage than just the power socket
> when I trod on it.
SIGABRT is a problem in your code. If you aren`t seeing stuff in the kernel
log then it almost certainly isn`t a hardware fault. It is a very special
skill to have a hardware fault without spewing lots of stuff there.
Post the code somewhere and someone can take a look. Otherwise you need to
use the development tools available to you to debug the problem.
Theo
--- tin/1.8.3-20070201 ("Scotasay") (UNIX) (Linux/5.10.0-22-amd64 (x86_64))
* Origin: University of Cambridge, England (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441