Hello,
This could be our C code (forgetting to do an INCREF or doing an undesired
DECREF) but I would have thought lots of other people would be getting the
same. (Although not guaranteed.)
Another option is that Python and Analysis were compiled with different
copies of Tcl/Tk. But this normally leads to an immediate crash, so I
would have thought that was unlikely. Do you have, or can you install,
the program "lsof"? If so, then do a "lsof -p" when Analysis is running
and see what libraries are being picked up.
Is there anyone else out there who has successfully run Analysis in Suse
10.2 64 bit (which I assume is what the "_64" means)?
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
>
|