-
Notifications
You must be signed in to change notification settings - Fork 33
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
valgrind issues #868
Comments
Adding -g to GLOBAL_FLAGS gives tiny more details
|
The leak is reported in mg5amcnlo/mg5amcnlo#109 |
(Note: this is one example of #207 about testing code through valgrind) |
The uninitialised value is reported in mg5amcnlo/mg5amcnlo#111 After applying both patches above, there are now no valgrind issues in madevent_fortran
Note, the rotxxx crash is still there instead in madevent_cpp
I will now check valgrind also on madeven_cpp |
I have tried to run valgrind on madevent_cpp but this hangs...
After 200 minutes (more than 3 hours) this was still running...
I will abandon this line of tests forthe moment |
…grind leak warning madgraph5#868 ==3682257== 544 (32 direct, 512 indirect) bytes in 1 blocks are definitely lost in loss record 3 of 3 ==3682257== at 0x719786F: malloc (vg_replace_malloc.c:381) ==3682257== by 0x7404CC8: ??? (in /usr/lib64/libgfortran.so.5.0.0) ==3682257== by 0x7647C63: ??? (in /usr/lib64/libgfortran.so.5.0.0) ==3682257== by 0x7635319: ??? (in /usr/lib64/libgfortran.so.5.0.0) ==3682257== by 0x76357FC: _gfortran_st_open (in /usr/lib64/libgfortran.so.5.0.0) ==3682257== by 0x47AA9F: open_file_ (open_file.f:40) ==3682257== by 0x432C91: MAIN__ (driver.f:151) ==3682257== by 0x40268E: main (driver.f:301) ==3682257==
…clscales (workaround for valgrind undefined behaviour madgraph5#868) ==3687827== Conditional jump or move depends on uninitialised value(s) ==3687827== at 0x425E73: setclscales_ (reweight.f:1230) ==3687827== by 0x4284D9: update_scale_coupling_vec_ (reweight.f:1876) ==3687827== by 0x436BC7: dsig_vec_ (auto_dsig.f:316) ==3687827== by 0x45AFEA: sample_full_ (dsample.f:208) ==3687827== by 0x4331AD: MAIN__ (driver.f:257) ==3687827== by 0x40268E: main (driver.f:302) ==3687827== Uninitialised value was created by a stack allocation ==3687827== at 0x424051: setclscales_ (reweight.f:555)
A couple of valgrind issues (running vaglrind over fortran) have been addressed. The issue remains that running valgrind over the cudacpp madevent instead hangs. This should eventually be opened in a new issue. I am closing this for simplicity as the most urgen issus have gone. |
PS A couple of comments from extra tests
So I would say that I completed this valgrind investigation for now... |
Since we are not yet converging on some issues like the rotxxx segfault #855 and the possible fix with volatile in #857, in parallel I am also running some checks with valgrind.
On the current upstream/master 286280f, using the same code I used for the #855 reproducer described here, #857 (comment) , I try this valgrind, to start with on Fortran ONLY.
Note that 32 events are enough, the cpp still crashes.
I do this valgrind
And this tells me
The text was updated successfully, but these errors were encountered: