On Wed, 2006-02-08 at 16:01 +0000, Baruch Even wrote:
> Omer Zak wrote:
> > The evidence points at some process, unknown to me, which gets scheduled
> > in Tkinter's main loop, and which takes about 1sec. While this process
> > is executing, the GUI is unresponsive and my own processes execute later
> > than their scheduled times.
> >
> > Any advice how to find that process and figure out what it does and why?
>
> I'd start with stracing the python process to try and see if it is
> something wrong or maybe there is a sleep(1) command done there.
There were no sleep() calls. strace was not useful.
> Other than that I can only think about look at Tkinter code and changing
> it to print what it does so you can trace it when it runs to see what
> happens.
>
> It is also possible to compile the Tkinter.so object with debug symbols
> and use gdb to just print at breakpoints and continue immediately,
> though latency of break points will be higher than prints.
I googled for information about getting Tcl/Tk to call my own callback
function before/after processing each event in the event loop, but found
no such information.
Is there any Tcl/Tk maven in the group who can point me at getting a
trace of the events processed by Tk main loop (I can issue Tcl commands
by using the tk.call() function)?
Thanks,
--- Omer
--
Every good master plan involves building a time machine. Moshe Zadka
My own blog is at http://tddpirate.livejournal.com/
My opinions, as expressed in this E-mail message, are mine alone.
They do not represent the official policy of any organization with which
I may be affiliated in any way.
WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html
