From: FyD (fyd_at_q4md-forcefieldtools.org)
Date: Mon Nov 05 2007 - 15:14:20 CST

Dear Peter,

> what version of VMD are you using? There had been a memory corruption
> problem in this plugin that was fixed fairly recently, and only
> manifested on some architectures (I believe including linux64).

The problem only appends on LINUX-64bits with VMD-32 or VMD-64 bit versions.
I used the 1.8.6 versions, all downloaded this morning.

On linux 32bits with VMD-opengl, I can display the file (the unique atom).

> On second thought, this appears to happen in even the latest builds.
> Looks like there's an issue with having an empty bond list; I'll have to
> track down exactly what. Thanks for pointing this out.

Yes, but only for 64bit version.

Thanks, regards, Francois

>> I load the following Tripos mol2 file in VMD.
>> This file is constituted of a unique atom:
>>
>> @<TRIPOS>MOLECULE
>> METH
>> 1 0 1 0 1
>> SMALL
>> USER_CHARGES
>> @<TRIPOS>ATOM
>> 1 H14 0.131341 1.070393 -0.105211 H 1 METH 0.0414
>> @<TRIPOS>BOND
>> @<TRIPOS>SUBSTRUCTURE
>>
>> Under linux 32bits, this file can be read under VMD-opengl.
>> Under linux 64bits, this file can be read under VMD-64bits, VMD crashes.
>>
>> Any idea why ?