Sibylle Koczian wrote: > Yes, that is right. The dGrid problem starts with revision 4572.
Ok, let's find out what line triggers it. Here's your strategy. 1) cd dabo;svn up -r 4572 2) edit dabo/ui/uiwx/dGrid.py 3) find the _paintHeader() method 4) at the top of the method, put 'print "_paintHeader() 1"' 5) at the bottom of the method, put 'print "_paintHeader() 2"' 6) run the dGrid self-test (python dGrid.py) 7) did any of those print statements print before crashing? If you got "_paintHeader() 1" but not "_paintHeader() 2" then you know that something in that method is causing the problem. Move each print statement closer to each other by 10 lines, and run again. Do steps 6-7 until you've isolated the offending line. > But: I just tried it with an OpenSuse LiveCD on the same machine. It was a > hassle to get Dabo to work (a LiveCD isn't really very suited for the > installation of additional packages), but when I finally had it, the demo, > including the dGrid example, worked flawlessly. Just as it does on my old and > slow Xubuntu machine. > So it really seems to be my Gentoo installation and not a bug in Dabo. Could > it be that it's a version of gcc which is too old? Gentoo uses 4.1.2, > everything above that is marked as unstable. Suse 11.0 uses 4.3.1 (or > possibly 4.3.2, not sure). Could be something like that, but let's find the line that causes the problem first: could be a different way of doing it that works for all. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
