From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Tue Aug 11 17:40:48 EDT 2020 Received: from abbatoir.fios-router.home (pool-74-101-2-6.nycmny.fios.verizon.net [74.101.2.6]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id a9de2b8e (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO); Tue, 11 Aug 2020 14:40:33 -0700 (PDT) Message-ID: <24E1197B54F67C5680E6D1DA3F7D9B89@eigenstate.org> To: sirjofri+ml-9front@sirjofri.de, 9front@9front.org Subject: Re: [9front] Imap bug after new date libs Date: Tue, 11 Aug 2020 14:40:32 -0700 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: shared lossless deep-learning descriptor > Hello all, > > since ori's new date library the imap4d breaks. > > The error in /sys/log/imap4d is: > > imap4d 37122: suicide: sys: trap: fault read addr=0x95 pc=0x2194a7 > > I'll try to fix that bug and the date bug (see other mails) when I have the time. For now I rolled back to the previous version via hg. > > sirjofri Hm -- I had avoided committing to imap4d because I haven't tested it enough -- is this with or without the patch that I sent you? Can you get the stack trace? you should be able to connect to the dead process with acid and run lstk() to get the stack trace. acid 37122 acid: lstk()