[gmx-users] Re: debug from floating exceptions in g_energy (v3.1)

[Lynne E. Bilston]

>
> >>You could also try to select a lower level of optimization by setting
> >>CFLAGS to e.g. "-g" before running configure, but if version 3.0 worked I
> >>really doubt it is a compiler bug (although we've seen quite a few of
> >>those ...).
> >
> >With the -g compiler option v3.1.1 compiles, but I get the same floating
> >exception in g_energy. I'm happy to try the debugging, as per Berk's
> >suggestion, if someone tells me how to do it!
>Good! That means you can debug it:
>after the crash you write:
>dbx `which g_energy`
>dbx>where
>  ... lots of output ...
>dbx>quit
>
>then you forward the output to the list.

I used dbx on the 3.1.1 source as follows:

(dbx) run g_energy -f pr

(selection of the energy terms etc snipped)

Back Off! I just backed up energy.xvg to #energy.xvg#
Reading frame      0 time    0.000           signal Floating point 
exception at   [do_enx:296 +0x14,0x12001def4]         Source not available

(dbx) where
 >  0 do_enx(fp = 0, fr = 0x14003d360) ["enxio.c":296, 0x12001def4]
    1 main(argc = 1, argv = 0x11fffc018) ["g_energy.c":922, 0x12001182c]


That's all I got. Does that mean something to someone?

-Lynne