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 6612 invoked from network); 15 Jul 2021 23:32:17 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 15 Jul 2021 23:32:17 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 1ess; Thu Jul 15 19:05:25 -0400 2021 Received: from abbatoir.myfiosgateway.com (pool-74-108-56-225.nycmny.fios.verizon.net [74.108.56.225]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id e260c8d4 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Thu, 15 Jul 2021 16:05:00 -0700 (PDT) Message-ID: <5DC2C69CF1837BEADA2CE21DC0DEBDF0@eigenstate.org> To: 9front@9front.org Date: Thu, 15 Jul 2021 19:04:58 -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: abstract agile injection component Subject: Re: [9front] Re: speaking of screenlock Reply-To: 9front@9front.org Precedence: bulk Quoth Stuart Morrow : > Actually, I don't get what it is about screenlock in the first place > that different procs can't access each other's malloc'd objects. It > seems other programs can do this just fine. > See RFMEM in rfork(2). Though, I don't see anything in screenlock that would prevent it. What makes you think they can't access each other's malloc'ed objects?