From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30500 invoked by alias); 21 Feb 2007 14:55:30 -0000 Received: (qmail 30486 invoked by uid 22791); 21 Feb 2007 14:55:28 -0000 X-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 21 Feb 2007 14:55:22 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l1LEtKpf021699 for ; Wed, 21 Feb 2007 09:55:20 -0500 Received: from pobox.hsv.redhat.com (pobox.hsv.redhat.com [172.16.16.12]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1LEtJND030803 for ; Wed, 21 Feb 2007 09:55:19 -0500 Received: from [10.11.14.72] (vpn-14-72.rdu.redhat.com [10.11.14.72]) by pobox.hsv.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l1LEtI0D014638 for ; Wed, 21 Feb 2007 09:55:19 -0500 Message-ID: <45DC5D51.3000209@redhat.com> Date: Wed, 21 Feb 2007 14:55:00 -0000 From: Phil Muldoon User-Agent: Thunderbird 1.5.0.9 (X11/20061219) MIME-Version: 1.0 CC: Frysk List Subject: Re: Status report References: <1172066082.3457.72.camel@dijkstra.wildebeest.org> In-Reply-To: <1172066082.3457.72.camel@dijkstra.wildebeest.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00155.txt.bz2 Mark Wielaard wrote: > Hi, > > Since there is so much talk about how to better coordinate and because I > actually don't like (long) phone meetings for status tracking, here are > some things I have recently been working on, some things that still need > some work, but that I am not currently working on and my current > priorities. > Good idea, here are mine: - Static core file analysis. I'm writing LinuxCore{Host|Proc|Task} and the corresponding state machines for each of the LinuxLinuxCore{Host|Proc|Task}State. The challenge here is to construct a peer system to LinuxPtrace like Procs and Tasks. This will be simpler, but will cover a lot of ground. - In doing above, writing up a note reader to read notes from core files to construct the proc/tasks. I thought I had this done, but I made the mistake that the core file architecture has to be decided on runtime, not via defines, in the case of looking at a x86 core file on a PPC32 machine. Investigating the ebl function pointer routines in elf-utils for this. - Writing up a the relative interfaces to translate memory accesses the Task and converting them to the file offset reads in the core file. - Looking at how to fail on operations that ptrace tasks does "ie step" that core file tasks cannot do. Ignore and eat the call? Throw an unchecked exception? - Investigating whey Procs/Tasks need to know so much about their initial starting states. Tasks are worse here by a larger magnitude. Right now Task.java sets ptrace states which is given Task,java information beyond its scope. - Briefly looked at ktrace/kdump Regards Phil