TTM problème in last svn version: glibc detected

Dear all,

I have problem using TTM (with manybody, misc and user-misc packages) that was not occuring in previous svn versions:

fix 2 all ttm/mod 1354684 TTM_param.txt 20 20 20 T_elec.in 1000 T_elec.out
*** glibc detected *** /path/mylammps/src/lmp_mpi: double free or corruption (out): 0x0000000001c0f360 ***
...

the code have been compiled whith intel (I added -restrict to the cc_flags) without errors.

Do you have any idea of the changes that create this issue and how to solve it?

I read in previous mailing list that a patch was missing...

Thanks for all

Antoine Jay

Dear all,

I have problem using TTM (with manybody, misc and user-misc packages) that was not occuring in previous svn versions:

but, pray, which version of LAMMPS exactly are you using right now?

fix 2 all ttm/mod 1354684 TTM_param.txt 20 20 20 T_elec.in 1000 T_elec.out
*** glibc detected *** /path/mylammps/src/lmp_mpi: double free or corruption (out): 0x0000000001c0f360 ***
...

the code have been compiled whith intel (I added -restrict to the cc_flags) without errors.

Do you have any idea of the changes that create this issue and how to solve it?

nothing specific. the message clearly indicates a bug. since last
summer, there has been a concerted effort, to improve the code quality
in LAMMPS with a variety of tools and changes to the source to improve
consistent behavior. this may expose bugs that went previously
unnoticed and those are the worst kind of bugs, as they just silently
and sometimes very subtly corrupt your simulations.

to track this down, it would be necessary to have a suitably small and
minimal test input that can quickly reproduce this behavior with the
latest svn/git sources.

I read in previous mailing list that a patch was missing...

what mailing list? what message? what patch? nobody can provide useful
advice on such vague and uncomfirmable statements.

axel.