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=1.1 required=5.0 tests=DATE_IN_PAST_06_12 autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 28706 invoked from network); 28 Jan 2021 20:40:06 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 28 Jan 2021 20:40:06 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 1ess; Thu Jan 28 07:57:55 -0500 2021 Message-ID: Date: Thu, 28 Jan 2021 13:57:44 +0100 From: cinap_lenrek@felloff.net To: 9front@9front.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: core element SOAP content-driven STM frontend Subject: Re: [9front] acid:V: line in mkfile for pc64 Reply-To: 9front@9front.org Precedence: bulk > How to use this line for debugging pc64 kernel? i dont think this is used by anything. kernel debugging can be done like: acid -k -lkernel $pid then type kinit(), and execute its output in the acid prompt, which generates the needed acid files and includes. i dont know why that acid rule was there in the mkfile. sometimes i use acid files to quickly get the effective size a struct for estimation of memory requirements. maybe this was there as a shortcut for it? -- cinap