 |
 |
Hello, It looks like this error is down to a change in the Python C implementation between Python 2.4 and Python 2.5. We noted this change here (it must have been exactly because of this error arising) in January and versions 1.0.13 and 1.0.14 of Analysis should work with Python 2.5. But versions earlier than 1.0.13 will not work with Python 2.5. Wayne On Tue, 5 Jun 2007, David Horita wrote: > Hi, > I've been trying to run analysis on a Suse 10.2/Linux x86_64 system and > have run into the "glibc detected *** python: double free or corruption > (out)" error message when a window is drawn. This was discussed last year > (item 001805); is there a fix/workaround? are my python/tk/tcl > installations the problem? > Thanks, > David Horita >