Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uninitialised values #2

Open
zingale opened this issue Jun 12, 2018 · 3 comments
Open

uninitialised values #2

zingale opened this issue Jun 12, 2018 · 3 comments

Comments

@zingale
Copy link
Member

zingale commented Jun 12, 2018

Valgrind gives:

==19141== Conditional jump or move depends on uninitialised value(s)
==19141==    at 0x53FB23E: ??? (in /usr/lib64/libgfortran.so.5.0.0)
==19141==    by 0x53FB623: ??? (in /usr/lib64/libgfortran.so.5.0.0)
==19141==    by 0x53FC5FD: ??? (in /usr/lib64/libgfortran.so.5.0.0)
==19141==    by 0x53FD344: ??? (in /usr/lib64/libgfortran.so.5.0.0)
==19141==    by 0x493524: __boxlib_MOD_boxlib_initialize (boxlib_f.f90:32)
==19141==    by 0x69DEC1: MAIN__ (main.f90:13)
==19141==    by 0x69E298: main (main.f90:3)

for both Maestro and the Microphysics unit tests.

@WeiqunZhang
Copy link
Member

Which test did you do?

Using MAESTRO development branch, I built in Exec/TEST_PROBLEMS/rt/ with FBOXLIB_HOME=... make MPI=t, and ran with mpiexec -n 4 valgrind --leak-check=yes --log-file=vallog.%p ./main.Linux.gfortran.mpi.exe ... I didn't see the error above. It did report errors. But it was

==12269==    at 0x61FC03: __make_pi_cc_module_MOD_make_pi_cc_2d (make_pi_cc.f90:174)
==12269==    by 0x622211: __make_pi_cc_module_MOD_make_pi_cc (make_pi_cc.f90:74)
==12269==    by 0x41A0EE: __advance_timestep_module_MOD_advance_timestep (advance.f90:1390)
==12269==    by 0x7F2BAA: varden_ (varden.f90:543)
==12269==    by 0x5BCF7F: MAIN__ (main.f90:19)
==12269==    by 0x4055FC: main (main.f90:3)

@zingale
Copy link
Member Author

zingale commented Jun 18, 2018

oh... it was one compiled without MPI. So it is something in the wrappers.

@WeiqunZhang
Copy link
Member

Without MPI, I don't see the error either. This is puzzling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants