Skip to content

[ML] Fix potential out-of-bounds read#2385

Merged
tveasey merged 3 commits intoelastic:mainfrom
tveasey:out-of-bounds-read
Aug 10, 2022
Merged

[ML] Fix potential out-of-bounds read#2385
tveasey merged 3 commits intoelastic:mainfrom
tveasey:out-of-bounds-read

Conversation

@tveasey
Copy link
Copy Markdown
Contributor

@tveasey tveasey commented Aug 10, 2022

Debugging an intermittent SIGSEGV triggered by another change I'm working on showed up this potential out-of-bounds read. It would happen very infrequently. It was introduced by #1537.

Copy link
Copy Markdown

@droberts195 droberts195 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tveasey tveasey merged commit fdcd0a0 into elastic:main Aug 10, 2022
@tveasey tveasey deleted the out-of-bounds-read branch August 10, 2022 17:22
edsavage added a commit to edsavage/ml-cpp that referenced this pull request Mar 20, 2026
The "Analyze build failure" step ran successfully on Build elastic#2385,
correctly identifying the deliberate #error as a code bug with high
confidence. Reverting to restore normal builds.

Made-with: Cursor
edsavage added a commit to edsavage/ml-cpp that referenced this pull request Mar 24, 2026
The "Analyze build failure" step ran successfully on Build elastic#2385,
correctly identifying the deliberate #error as a code bug with high
confidence. Reverting to restore normal builds.

Made-with: Cursor
edsavage added a commit to edsavage/ml-cpp that referenced this pull request Mar 26, 2026
The "Analyze build failure" step ran successfully on Build elastic#2385,
correctly identifying the deliberate #error as a code bug with high
confidence. Reverting to restore normal builds.

Made-with: Cursor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants