2010/5/22 Mengjuei Hsieh <mjhsieh.gmail.com>
> I am not sure why accessing aAtom's fFlags item in that particular
> code triggers a segfault, perhaps it's not always
> allocated/initialized (?). This smells like a source code level
> problem, however it seems to be fc12 specific.
>
> Best,
> --
> Mengjuei
>
>
> Loading library: /home/mjhsieh/amber11/dat/leap/lib/all_nucleic94.lib
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000000041ba9b in bAtomCoordinationSaturated (aAtom=0x0) at atom.c:356
> 356 if ( bAtomFlagsSet( aAtom, ATOMPERTURB ) ) {
>
[*.*]$ uname -a
Linux *-127.fc12.x86_64 #1 SMP Sat Nov 7 21:11:14 EST 2009 x86_64 x86_64
x86_64 GNU/Linux
[*.*]$ tleap
-I: Adding /opt/amber11/dat/leap/prep to search path.
-I: Adding /opt/amber11/dat/leap/lib to search path.
-I: Adding /opt/amber11/dat/leap/parm to search path.
-I: Adding /opt/amber11/dat/leap/cmd to search path.
Welcome to LEaP!
(no leaprc in search path)
> loadoff all_nucleic94.lib
Loading library: /opt/amber11/dat/leap/lib/all_nucleic94.lib
> desc RAN
UNIT name: RAN
Head atom: null
Tail atom: null
Contents:
R<RAN 1>
> quit
Quit
Look for way out elsewhere.
--
Sincerely,
Dmitry Mukha
Institute of Bioorganic Chemistry NAS, Minsk, Belarus
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Sat May 22 2010 - 04:30:04 PDT
