From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <58698c1354018b0ea553bb777dd99e04@yyc.orthanc.ca>
References: <dd6fe68a1002081655h22ea1901te5caa7f82326a635@mail.gmail.com>
	<58698c1354018b0ea553bb777dd99e04@yyc.orthanc.ca>
Date: Mon,  8 Feb 2010 23:24:57 -0200
Message-ID: <32d987d51002081724v4bf529d2he9a9ee1b3d2ec2e4@mail.gmail.com>
From: "Federico G. Benavento" <benavento@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] acid tools for tracking leaking fd's
Topicbox-Message-UUID: d0c93124-ead5-11e9-9d60-3106f5b1d025

setfdtag(getcallerpc(&s))?

On Mon, Feb 8, 2010 at 11:04 PM, Lyndon Nerenberg (VE6BBM/VE7TFX)
<lyndon@orthanc.ca> wrote:
>> cat /proc/$pid/fd
>
> I already know the bloody thing is open :-P
>
> I just wondered if someone had come up with some glue to intercept
> open()/close()/dup()/etc and track the fd's in an acid list, or
> something similar.
>
>
>



--
Federico G. Benavento