From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 11801 invoked from network); 1 Oct 2023 04:15:35 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 1 Oct 2023 04:15:35 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Sun Oct 1 00:13:46 -0400 2023 Received: from abbatoir (pool-108-6-24-2.nycmny.fios.verizon.net [108.6.24.2]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 2601efa1 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Sat, 30 Sep 2023 21:13:43 -0700 (PDT) Message-ID: <4F3D2C9093B9D1B31C1623A8A7A7B41A@eigenstate.org> To: 9front@9front.org Date: Sun, 01 Oct 2023 00:13:41 -0400 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: CMS browser ActivityPub hardware session grid Subject: Re: [9front] upas/fs lstk(), one more time Reply-To: 9front@9front.org Precedence: bulk Quoth sl@stanleylieber.com: > i backed up my mbox and added messages back in batches, checking after > each batch that upas/fs was still able to open it. i did this until i > found a specific message upas/fs choked on. > > sl is it possible to reproduce it with just that message? would you be comfortable sending it over to someone for debugging?