Hello everyone!
I am trying to redesign the protein-DNA interface to introduce novel interactions between a protein and a DNA molecule using the RosettaDNA application suite.
I am getting this error after running the program. Can you help to fix this?
There are 19 dna positions:
60 (pdb B 1) DT <=> DA 96 (pdb B 37)
61 (pdb B 2) DA <=> DT 95 (pdb B 36)
62 (pdb B 3) DA <=> DT 94 (pdb B 35)
63 (pdb B 4) DT <=> DA 93 (pdb B 34)
64 (pdb B 5) DA <=> DT 92 (pdb B 33)
65 (pdb B 6) DC <=> DG 91 (pdb B 32)
66 (pdb B 7) DG <=> DC 90 (pdb B 31)
67 (pdb B 8) DA <=> DT 89 (pdb B 30)
68 (pdb B 9) DC <=> DG 88 (pdb B 29)
69 (pdb B 10) DT <=> DA 87 (pdb B 28)
70 (pdb B 11) DC <=> DG 86 (pdb B 27)
71 (pdb B 12) DA <=> DT 85 (pdb B 26)
72 (pdb B 13) DC <=> DG 84 (pdb B 25)
73 (pdb B 14) DT <=> DA 83 (pdb B 24)
74 (pdb B 15) DA <=> DT 82 (pdb B 23)
75 (pdb B 16) DT <=> DA 80 (pdb B 21)
76 (pdb B 17) DA <=> DT 79 (pdb B 20)
77 (pdb B 18) DG <=> DC 78 (pdb B 19)
81 (pdb B 22) DA (unpaired)
Segmentation faults are somewhat hard to debug, as they can be caused by a number of very different reasons, and so just "Segmentation Fault" by itself is none too helpful.
If possible, could you recompile with `mode=debug` and run the linuxgccdebug (or your platform's equivalent) version of the application? The debug version contains additional checks that, while slowing down the run, make figuring out what might be wrong a bit easier.
The other thing to do is to be extra careful in re-reviewing your inputs to make sure everything is as it should be. Generally Segmentation Faults arise when a condition the original programmer didn't anticipate happened. That should ideally result in an interpretable error message, but sometimes a combination of unexpected inputs makes it through.