[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Execution replay for Qt/KDE applications
From:       David Faure <faure () kde ! org>
Date:       2004-10-20 20:43:59
Message-ID: 200410202244.00081.faure () kde ! org
[Download RAW message or body]

On Wednesday 20 October 2004 22:36, Oliver Oppitz wrote:
> On Monday 18 October 2004 00:03, Oliver Oppitz wrote:
> 
> > One can either "replay at recording speed" (with the same delays), or  
> > "replay at full speed",
> > which is more useful for debugging since the replay is very fast.
> What does "with the same delays" mean precisely? If the tool measures the  
> delay (e.g. in ms, us) and reproduces this delay in the replay this does  
> not _necessarily_ guarantee identical execution patterns because:
> - the machine may have different load during the replay
> - the precision of ms may not be good enough

Yes.

> To guarantee an identical replay one needs reconstruct the exact call  
> graph i.e. insert the invents in the same invocation of the event loop.

That's only one solution to the problem (which would involve some kind
of valgrind integration - a rather complex and non-portable solution...).

Another solution (provided by KDX) is to insert synchronization points. 
While recording you can say "now wait for this widget to exist" or 
"wait for this widget to have the property foo with value bar", etc.

> Also, an execution-replay tool would need to capture all input from files  
> that the program works on. Does KDExecutor do this?

I'm not sure, actually. Kalle?

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]