On Wed, 2015-12-09 at 10:32 -0800, Nikolaus Rath wrote: > (gdb) bt > #0 0x0000000001010750 in H5FL_reg_calloc () > #1 0x0000000000fa64ea in H5A_create () > #2 0x0000000000fa0611 in H5Acreate2 () > #3 0x0000000000f8f3be in h5acreate_c_ () > #4 0x0000000000f897b7 in h5a_mp_h5acreate_f_ () > #5 0x0000000000b99fc7 in h5dump_attr_int (loc_id=<optimized out>, > f=<optimized out>, name=..., > .tmp.NAME.len_V$1086=<optimized out>) > at /home/nrath/Q2D/utils/src/taehdf5.f90:1936 > #6 h5append_data_double_0d (group_id=1, > f=<error reading variable: Cannot access memory at address > 0xa000008>, name=..., > .tmp.NAME.len_V$1cd8=272) > at /home/nrath/Q2D/utils/src/taehdf5.f90:4193 > #7 0x0000000000b248e7 in plot_m::plots (idt=1) > at /home/nrath/Q2D/LamyRidge/src/model/plot_hdf5.f:144 > #8 0x0000000000b3b723 in lr_mod_m::check_dt (idt=1) > at /home/nrath/Q2D/LamyRidge/src/model/LR_model.F:487 > #9 0x0000000000b272e4 in lr_mod_m::lr_step (idt=1, > dt_r=<error reading variable: Cannot access memory at address > 0xa000008>, t_r=0) > at /home/nrath/Q2D/LamyRidge/src/model/LR_model.F:252 > #10 0x0000000000b261de in lr_model () > at /home/nrath/Q2D/LamyRidge/src/model/LR_model.F:544 > > Interestingly enough, but stacktraces are incorrect: gdb is missing > the call to taehdf5_mp_h5append_data_double_0d_, and valgrind is > missing the call to h5dump_attr_int. The gdb stacktrace contains a call to h5append_data_double_0d (frame 6). So, as far as I can see, the gdb stacktrace is similar with -O1 and -O2 (if we ignore small details like the namespace taehdf5::) (I know nothing about fortran, so no idea if that is a namespace or whatever).
When using gdb, you might maybe find more info using e.g. info frame 5/6/7 Philippe ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
