Hi Tim,
If Chimera starts use Chimera menu Help / Report a Bug.... This
will give us info about your operating system, graphics and
Chimera version. Chimera crashes are usually due to having a
buggy graphics driver installed on your computer. Updating, or
installing a graphics driver is usually the solution.
Tom
-------- Original Message --------
Subject: Re: [Chimera-users] segmentation fault
From: Tim Richardson
To:
chimera-users@cgl.ucsf.edu
Date: 10/25/12 1:51 PM
Hi,
I'm getting segmentation faults when using chimera. I tried
to produce a backtrace, but got an error:
[tim@nest ~]$ gdb chimera core.3777
GNU gdb (GDB) Fedora (7.4.50.20120120-50.fc17)
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software: you are free to change and
redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type
"show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
"/usr/bin/chimera": not in executable format: File format not
recognized
[New LWP 3777]
[New LWP 3787]
Core was generated by `/opt/UCSF/Chimera-1.6.2/bin/python2.7
/opt/UCSF/Chimera-1.6.2/share/__main__.py'.
Program terminated with signal 11, Segmentation fault.
#0 0xb578ddc7 in ?? ()
(gdb) bt
#0 0xb578ddc7 in ?? ()
#1 0x0963be90 in ?? ()
Backtrace stopped: previous frame inner to this frame
(corrupt stack?)
Could you advise how I might avoid a segmentation fault and what
I'm doing wrong with the backtrace. Is there anything I can do
short of installing a VM and running the windows version?
Many thanks,
Tim Richardson
@timrich
_______________________________________________
Chimera-users mailing list
Chimera-users@cgl.ucsf.edu
http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users