Re: Status report

[Phil Muldoon <pmuldoon@redhat.com>]

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