Re: EventViewer Rewrite

[Sami Wagiaalla <swagiaal@redhat.com>]

> The new EventViewer stuff looks really impressive. Awesome work!
>   
Thanx :)
> I'd have to second Phil's questions though - I think we need some
> semblance of time, or relative time between events on the X axis.
>   
The model I am basing this on and the one we already know works is that
of printf debugging, were the user doesn't really care about time.

The design of the new EventViewer makes it really easy to add a time tick
(just another event). A reasonable suggestion made by Cagney when we
had this dicussion a while back was to add a time tick every time the event
loop loops.
> Another question: Why do the second and third lines co-mingle? Why
> doesn't 22441 have events occurring on a single line like 22437? Or is
> that because the events on the third line have a different tag than the
> events on the first and second lines?
>   
The first line is the process which is a cumilation of all the events 
occuring
within the process regardless of what thread they blong to.

the second line is the main thread of the process. Until a second thread is
spawned the main thread is identicall to the process. because all events
occure on the main thread.

The third line represents a second thread which is not spawned untill the
event that says "cloned by 22437" which is the thread id of the thread which
called clone.

does that make sense ^ ?