On Fri, May 21, 2010 at 10:49 PM, Mengjuei Hsieh <mjhsieh.gmail.com> wrote:
> I am pretty sure that it's not related after I really started to look
> into the segfaults. At first glance, I found that on FC12(x86_64) I
> can trigger teLeap segfault every time I ran "loadOff
> all_nucleic94.lib". More to come, after I can finish to update every
> package on this fc12 box..
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 ) ) {
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Sat May 22 2010 - 02:30:03 PDT
