On Fri, Jun 24, 2011 at 9:18 AM, Wojtek wrote: > Of course there was a bug in example was send, but > it was a fast typing bug. > I send you printscreen with correct example. > There is the same 100% CPU pyclew problem.
I cannot reproduce it with your last test case, using pyclewn 1.6.py2, gcc (Debian 4.3.2-1.1) 4.3.2 and GNU gdb (GDB) 7.2. Can you set pyclewn traces and send me the logfile. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
