A bit related to the thread about dropping gtk1 versions: has anyone experienced this and perhaps could provide a fix/explanation?
Symptoms: (get-monomer three-letter-code) makes gtk2 (!) centos-4 coot crash on RHEL4, e.g. with GOL: --- (monomer-molecule-from-3-let-code "GOL" "") throw from within critical section. /xtal/work/JED/coot/coot-Linux-i386-centos-4-gtk2/bin/coot: line 124: 23850 Aborted $coot_real $* coot-exe: "/xtal/work/JED/coot/coot-Linux-i386-centos-4-gtk2/bin/coot-real" coot-version: /xtal/work/JED/coot/coot-Linux-i386-centos-4-gtk2/bin/coot-real core: #f No core file found. No debugging --- Interestingly, get_monomer(three_letter_code) is fine, so is get-monomer in gtk1 redhat-8 coot, same machine, same circumstances. It gets more confusing: even though get-monomer fails, I can get away with replacing get-monomer with (monomer-molecule-from-3-letter-code three-letter-code "") in my scripts and extensions. The only thing I can think of is that this is a guile-issue, as centos-4 builds come with guile 1.8.5 while redhat builds have guile 1.6.8. Plus, I haven't come across anything that would give the above error message, other than libguile's throw. What do guile-experts say about this? I can't get my head around the difference between monomer-molecule-from-3-letter-code and get-monomer. Aren't they supposed to be one and the same thing? Why not use monomer-molecule-from-3-letter-code only? thanks, JED -------------------------------------------------------------------------- AstraZeneca UK Limited is a company incorporated in England and Wales with registered number: 03674842 and a registered office at 15 Stanhope Gate, London W1K 1LN. Confidentiality Notice: This message is private and may contain confidential, proprietary and legally privileged information. If you have received this message in error, please notify us and remove it from your system and note that you must not copy, distribute or take any action in reliance on it. Any unauthorised use or disclosure of the contents of this message is not permitted and may be unlawful. Disclaimer: Email messages may be subject to delays, interception, non-delivery and unauthorised alterations. Therefore, information expressed in this message is not given or endorsed by AstraZeneca UK Limited unless otherwise notified by an authorised representative independent of this message. No contractual relationship is created by this message by any person unless specifically indicated by agreement in writing other than email. Monitoring: AstraZeneca UK Limited may monitor email traffic data and content for the purposes of the prevention and detection of crime, ensuring the security of our computer systems and checking Compliance with our Code of Conduct and Policies.
