From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Duffy Subject: Re: Timing out waiting for vbd device *only when xend started with trace_start* Date: Mon, 14 Nov 2005 10:40:58 -0600 Message-ID: <4378BE1A.6060901@spamcop.net> References: <20051114115108.GA28247@leeni.uk.xensource.com> <43789319.9090609@spamcop.net> <20051114151038.GB16045@leeni.uk.xensource.com> <20051114163139.GH16045@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20051114163139.GH16045@leeni.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Ewan Mellor wrote: > On Mon, Nov 14, 2005 at 10:11:27AM -0600, Charles Duffy wrote: > >>It might be nice if the xend trace handler were expanded to print both >>current PID (or thread name) and timestamp when indicating that a line >>is being executed. > > Ask and ye shall receive an attachment. Nifty -- but not quite what I had in mind. I was thinking about modifying the *tracing*, not the *logging*; thus, it would be the code in xend/server/SrvDaemon.py:trace that would be impacted. This would allow for a substantially higher granularity -- seeing where we are not just on every log statement, but on every line executed by the interpreter.