When compiling 2.4.1 under 64bit linux (Mandrake 10.0,
lesstif 0.93.94-1mdk) for an athlon 64, viewmol
segfaults immediatly when starting. Here is a back trace:
#0 0x0000002a95faf676 in _XmCreateArrowPixmaps ()
from /usr/X11R6/lib64/libXm.so.2
#1 0x0000002a96665e3d in XtInitializeWidgetClass ()
from /usr/X11R6/lib64/libXt.so.6
#2 0x0000002a9666643b in XtInitializeWidgetClass ()
from /usr/X11R6/lib64/libXt.so.6
#3 0x0000002a966668ab in _XtCreateWidget () from
/usr/X11R6/lib64/libXt.so.6
#4 0x0000002a96696199 in _XtUnmergeTranslations ()
from /usr/X11R6/lib64/libXt.so.6
#5 0x0000002a9669649f in XtVaCreateManagedWidget ()
from /usr/X11R6/lib64/libXt.so.6
#6 0x0000000000436152 in makeMenu (parent=0x6efde0,
menu_type=2,
label=0x461eda "molecule", items=0x57b9e0) at
../makemenu.c:83
#7 0x000000000043603c in makeMenu (parent=Variable
"parent" is not available.
) at ../makemenu.c:113
#8 0x000000000042d767 in makeViewerMenu
(widget=0x5d1360) at ../init.c:242
#9 0x000000000042d591 in initViewer (argc=1,
argv=0x7fbffff4d8,
widget=0x5d1360) at ../init.c:191
#10 0x0000000000458f2f in main (argc=Variable "argc" is
not available.
) at ../viewmol.c:269
When compiled in 32 bit mode, it starts fine, but can't
execute python scripts and segfaults in the geo
optimization log window.
I know what it says in the documentation about casting
pointers to integers for 64bit sgi compilers, but on
x86-64 systems, pointers and integers are different
sizes, pointer 64 bits , integer 32. I have
encountered quite a bit of code that crashes and burns
because it assumes sizeof(void *)==sizeof(int). This
is the major difference between compiling in 64 and 32
bit modes, so you might think about it.
