From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <d176b4d351dd099aeef71109668784c9@coraid.com>
References: <20110725135837.GC27739@fangle.proxima.alt.za>
	<CADSkJJXdgwbLHikkJNo9d8wwidrk_biMNeV5O1QCbQmSWVAqSw@mail.gmail.com>
	<20110725151746.GD27739@fangle.proxima.alt.za>
	<d176b4d351dd099aeef71109668784c9@coraid.com>
Date: Mon, 25 Jul 2011 15:31:13 -0400
Message-ID: <CADSkJJW0AWstkrYxAw6Sd2hTkAGN17ViSCH_73NtCJFQtg3O1g@mail.gmail.com>
Subject: Re: [9fans] Lock loop in malloc()
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: lucio@proxima.alt.za
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 063510a2-ead7-11e9-9d60-3106f5b1d025

>> Following Erik's direction, it seems that the lock value is 0x0deadead,
>
> btw, there appears to be a typo in /sys/src/libc/386/tas.s. =C2=A0it shou=
ld be spelled
> to match other arches. =C2=A0for some reason all other arches use 0xdeadd=
ead.
> unfortunately, pool also uses 0xdeaddead so this typo is fortunate.

it still didn't give you any information.
you could have deduced that value from the program counter.