-
-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading a specific PDB file crashes Avogadro #1637
Comments
Thanks for opening your first issue here! Please try to include example files and screenshots if possible. If you're looking for support, please post on our forum: https://discuss.avogadro.cc/ |
If the crash happens during a drop event, the backtrace of the active thread is:
If the crash occurs with the File > Open menu, the backtrace is the following:
|
Fixes OpenChemistry#1637 Signed-off-by: Geoff Hutchison <[email protected]>
Because we do file loading in a separate thread, backtraces are unfortunately not very useful. I have a better trace from the command-line. Since we're using our own code, the PDB reader isn't quite as battle-tested as the Open Babel code. |
I had a look and there's at least one weird thing: it assumes all avogadrolibs/avogadro/io/pdbformat.cpp Line 147 in 7061aac
I tested with a simple PDB file with a selenium atom, which VMD and Mercury read fine, but Avogadro transforms the selenium into sulfur.
I've also looked at openbabel and it definitely trusts the element field: |
It's one thing if the SE is in the atom name, but SE in the element column is reliable. |
Signed-off-by: Geoff Hutchison <[email protected]>
Here are the build results |
Here are the build results |
Fix bug reported in #1637 with mis-parsing selenium atoms in PDB
Avogadro version:
Desktop version: (please complete the following information):
Describe the bug
Loading a specific PDB file crashes Avogadro
To Reproduce
Steps to reproduce the behavior:
Expected behavior
That PDB file loads fine with various software. At the very least, it should give an error but not crash.
The text was updated successfully, but these errors were encountered: