On Fri, Aug 27, 2010 at 10:55 AM, Rob wrote: > > Please find attached the log for the watch closing issue (3). I did > encounter the problem, but wasn't able to drive it in a very > controlled manner with the debug output. It did terminate > unexpectedly at the end (although I may have hit the wrong key by > mistake!). Hope you can make sense of it. Let me know if I can > provide more information. >
Hi Rob, Thanks for the logs, they are helpful. I have fixed the closing issue (3), see the last commit in the mercurial repository. Actually I was wrong: the problem could be reproduced systematically with gdb 7.1 (and probably 7.0 but not in gdb 6.8) before this fix. The logs show also that the unexpected termination of pyclewn is caused by pyclewn raising an exception. I believe that this is related to issues (1) and (2) and this should help in debugging these issues. I am still looking into this. It would be nice to have a log for the last part of (3), when the gdb print command and the watched window disagree. I will be away for few days, so fixing (1) and (2) will take a while. Xavier ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
