-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
TLeaf::ReadBasket invalid write in TMVA test #10010
Comments
Note that I'm completely unsure if this is really Cling's fault. If not, we have to re-assign accordingly. |
This isn't cling; it's TLeaf reading an |
Ok, can you update the issue title to something appropriate? |
Most likely the TTree is still pointing to older (user data) addresses. (The 'failing' function set the address of only 4 out 7 branches. i.e. missing a |
Still there, would be good if somebody could have a look. |
ping @Axel-Naumann @lmoneta @pcanal this is still there |
ping @Axel-Naumann @lmoneta @pcanal Jenkins and me can still reproduce... |
@hahnjo
but later:
In contrast, TestCrossValidationIntVar seems to correctly use two variables to properly read the tree and spectate:
|
Valgrind complains of:
|
TLDR: The interesting bit is that So the issue is that the address of the Int branch:
is still set to an address that uses to be on the stack (according to valgrind). How can it be possible, you may ask. Well ... looking at the result of
even before the call to This means that at point the It turns out that the
At which point the
solves the problem. |
Fixes root-project#10010 All the credit for this fix goes to pcanal and anaumann
Fixes #10010 All the credit for this fix goes to pcanal and anaumann
Fixes root-project#10010 All the credit for this fix goes to pcanal and anaumann
Fixes #10010 All the credit for this fix goes to pcanal and anaumann
Fixes root-project#10010 All the credit for this fix goes to pcanal and anaumann
After #10005 is merged, the test
TMVA-CrossValidation-Serialise
will fail due to astack-use-after-return
:Note: There may be other problems in the test after this issue is fixed. Please check locally with an instrumented build that the test passes afterwards!
The text was updated successfully, but these errors were encountered: