Sorry. I think there was a bug in 4322 which I believe I fixed a few
hours later. Please try 4323.
B
On 15/08/2012 01:34, Paul Emsley wrote:
On 15/08/12 00:24, Scott Classen wrote:
Hi Paul,
I received this message after the crash: [snip]
Hi Scott,
Thanks for that.
There will be a fixed
On 15/08/12 00:24, Scott Classen wrote:
Hi Paul,
I received this message after the crash: [snip]
Hi Scott,
Thanks for that.
There will be a fixed binary (revision r4323) available shortly.
Regards,
Paul.
Hi Paul,
I received this message after the crash:
[New Thread 13701]
[Thread debugging using libthread_db enabled]
Core was generated by
`/programs/coot-Linux-x86_64-centos-6-gtk2-python/bin/coot-real'.
Program terminated with signal 6, Aborted.
#0 0x2b54f07c98a5 in raise () from /lib64/li
On 14/08/12 21:06, Scott Classen wrote:
Hello,
I just downloaded the latest coot (4322) and attempted to luanch on a new
CentOS 6 machine. Coot was none too happy.
For me too (strangely enough). Investigating now...
Here is the output.
I'm not sure how to turn on debugging or core dumps,
On Tuesday, August 14, 2012 02:51:19 pm Scott Classen wrote:
> Hi Ethan,
>
> Here are the contents of the valgrind log file after running the following
> command:
>
> valgrind --tool=memcheck --leak-check=yes --num-callers=20
> --log-file=valgrind.log
> /programs/coot-Linux-x86_64-centos-6-gtk
Hi Ethan,
Here are the contents of the valgrind log file after running the following
command:
valgrind --tool=memcheck --leak-check=yes --num-callers=20
--log-file=valgrind.log
/programs/coot-Linux-x86_64-centos-6-gtk2-python/bin/coot
Doesn't mean much to me, but perhaps you or Paul might get
Hello,
I just downloaded the latest coot (4322) and attempted to luanch on a new
CentOS 6 machine. Coot was none too happy.
Here is the output.
I'm not sure how to turn on debugging or core dumps, but if that would be
useful I can redo this.
classen@samos:/home/classen 1012%
/programs/coot-Li
