From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <82c890d00706070203j3eb29d1bo4594ee4d4ccfe862@mail.gmail.com>
Date: Thu,  7 Jun 2007 11:03:50 +0200
From: "Gabriel Diaz" <gabidiaz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] how to use 9loaddebug
In-Reply-To: <20070607081916.C21D31E8C1C@holo.morphisms.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <82c890d00706070050k70262102l2b33a137168d4239@mail.gmail.com>
	<20070607081916.C21D31E8C1C@holo.morphisms.net>
Topicbox-Message-UUID: 7a5525e4-ead2-11e9-9d60-3106f5b1d025

hello

oh, thank you, should i submit a patch to 9load man page with this information?

gabi


On 6/7/07, Russ Cox <rsc@swtch.com> wrote:
> > is that the way 9loaddebug should be used or i missed something?
>
> 9loaddebug is a copy of 9load that is linked like a regular plan 9 executable,
> so that it can be used with acid (as shown by the commands that
> mk 9loaddebug prints).
>
> a typical use is when 9load crashes at PC 0x8001023a you run
>
>         % acid 9loaddebug
>         acid: map({"text", 0x80010000, 0x80090000, 0x00000020})
>         acid: src(0x8001023a)
>
> it is "debug" in the sense that it has debugging information
> usable by acid.
>
> it is not "debug" in the sense that it is a working binary
> that prints debugging info.  you'll need to put the original
> 9load back in order to boot again (use a plan 9 cd).
>
> russ
>
>