Fix potential out-of-bounds memory in IdealClusterBuilder#2079
Conversation
|
This is ready for review, but the gold creation is in progress so I kept it draft until that finishes. |
Validation ResultsSome validation samples failed! ❌
|
|
/run-validation |
|
The validation workflow is running here: https://github.com/LDMX-Software/ldmx-sw/actions/runs/27662256723. |
|
cascade_history does not run the IdealClusterBuilder... it actually just runs the PN, which has been stable so far. Let's see the next test |
Validation ResultsSome validation samples failed! ❌
|
|
/run-validation |
|
The validation workflow is running here: https://github.com/LDMX-Software/ldmx-sw/actions/runs/27695331269. |
tomeichlersmith
left a comment
There was a problem hiding this comment.
small, logical change that I'm worried about affecting the algorithm
|
/run-validation |
|
The validation workflow is running here: https://github.com/LDMX-Software/ldmx-sw/actions/runs/27696786470. |
Validation ResultsAll validation samples passed! ✅
|
I am updating ldmx-sw, here are the details.
Replace initializer-list vector assignments (= {val}) with push_back to avoid a compiler/ASAN warning about potential out-of-bounds memmove; this works because std::map::operator[] default-constructs an empty vector when the key doesn't exist, so push_back on it is safe without an explicit count check.
What are the issues that this addresses?
Resolves #1707
Check List