From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Mon, 25 Jul 2011 10:40:51 -0400
To: lucio@proxima.alt.za, 9fans@9fans.net
Message-ID: <5f67d89d44ac52871d38a7f5a4ff8c67@coraid.com>
In-Reply-To: <20110725135837.GC27739@fangle.proxima.alt.za>
References: <20110725135837.GC27739@fangle.proxima.alt.za>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Lock loop in malloc()
Topicbox-Message-UUID: 05e7f646-ead7-11e9-9d60-3106f5b1d025

could you snap(4) this process and mail me/put on sources the
compressed snap?  it's not really possible for this lock to be
held unless cpp has stepped on its lock and the resulting garbage
makes it look like the lock is set.

if you want to try some things yourself, i'm going to run
	; 8c -a /sys/src/cmd/cpp/macro.c > cpp.acid
	; acid -lcpp.acid $pid
	; (Lock)0x1f2f8
	; dump(0x1f2f8, 16, "\X")

to start off with and consider what to do next based on
the results.

- erik