VMD-L Mailing List

From: Joshua A. Anderson (joaander_at_umich.edu)
Date: Fri Mar 25 2011 - 12:54:56 CDT

I'm linking VMD against a by hand built FLTK 1.3.0rc3 (also tried 1.3.x-r8518), and macports installed tcl/tk 8.5.9.
--------
Joshua A. Anderson, Ph.D.
Chemical Engineering Department, University of Michigan

On Mar 24, 2011, at 10:56 PM, John Stone wrote:

> Joshua,
> What FLTK and Tcl/Tk are installed by your macports? I've done
> a number of 64-bit VMD builds exploring which variations don't trigger
> bugs in FLTK and Tcl/Tk (the new Cocoa-based GUI code these toolkits
> have to use on 64-bit OSX is much less stable than the old Carbon APIs
> used in the same libs running on 32-bit OSX ). I'm traveling until
> Monday, but when I get back I'll touch base with you on this again.
> I have probably seen the same problem you're seeing, but I don't have
> the tracebacks with me on the road, so I'll have to check when I
> return home.
>
> Cheers,
> John Stone
> vmd_at_ks.uiuc.edu
>
> On Tue, Mar 22, 2011 at 09:55:00AM -0400, Joshua A. Anderson wrote:
>> Hi all,
>>
>> Just updated my local MACOSXX86_64 python-enabled build of VMD to 1.9. It fixes most of the issues I had getting 1.8.7 to work - including the non-functional GLSL rendering mode (yay!). I did have to patch the source in a few places to get it to compile and run, though (patches attached).
>>
>> I'm building with the following configure options, and a modified configure script to use Python, tcl, and tk installed by macports (since the configure script overrides the env variables for mac builds......(: MACOSXX86_64 FLTKOPENGL FLTK TK IMD LIBTACHYON TCL PYTHON PTHREADS LP64
>>
>> I just have one remaining issue to solve - this build crashes on exit:
>> Info) Exiting normally.
>> vmd_MACOSXX86_64(23054,0x7fff707d3ca0) malloc: *** error for object 0x1011ec350: pointer being freed was not allocated
>> *** set a breakpoint in malloc_error_break to debug
>>
>> Program received signal SIGABRT, Aborted.
>> 0x00007fff835b5616 in __kill ()
>> (gdb) bt
>> #0 0x00007fff835b5616 in __kill ()
>> #1 0x00007fff83655cca in abort ()
>> #2 0x00007fff8356d6f5 in free ()
>> #3 0x00000001009ef0a4 in UnsetVarStruct ()
>> #4 0x00000001009ef2e5 in TclDeleteNamespaceVars ()
>> #5 0x00000001009bdfce in TclTeardownNamespace ()
>> #6 0x000000010094cf33 in DeleteInterpProc ()
>> #7 0x0000000100103690 in TclTextInterp::~TclTextInterp (this=0x101c3ce00) at TclTextInterp.C:266
>> #8 0x00000001000c6bfc in UIText::~UIText (this=0x101c3c860) at UIText.C:120
>> #9 0x00000001000cd2b7 in VMDApp::~VMDApp (this=0x100d122f0) at VMDApp.C:683
>> #10 0x00000001000eaf49 in main (argc=1, argv=0x7fff5fbff698) at vmdmain.C:68
>>
>> Anyone have any ideas where to start looking? I don't have this problem with VMD 1.8.7 compiled against the same python and tcl. TclTextInterp.C:266 is just Tcl_DeleteInterp(interp); It's kind of annoying because Mac OS X pops up a "do you wan to report this crash" dialog box every time.
>>
>
>
>
>
>>
>> --------
>> Joshua A. Anderson, Ph.D.
>> Chemical Engineering Department, University of Michigan
>>
>
>
> --
> NIH Resource for Macromolecular Modeling and Bioinformatics
> Beckman Institute for Advanced Science and Technology
> University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801
> Email: johns_at_ks.uiuc.edu Phone: 217-244-3349
> WWW: http://www.ks.uiuc.edu/~johns/ Fax: 217-244-6078
>
>