SmallVecN where N > 0 can cause memory corruption on the stack #2269

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.

Sign up for GitHub

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

Jump to bottom

Closed

pcwalton opened this issue Apr 29, 2014 · 4 comments

Labels

I-crash I-safety

Contributor

pcwalton commented Apr 29, 2014

Not good.

pcwalton added I-safety and removed A-platform/utils labels

Contributor

kmcallister commented May 17, 2015

Can you elaborate?

Member

SimonSapin commented Jun 2, 2015

@pcwalton Is this the same as servo/rust-smallvec#4 ?

sviter commented Oct 7, 2017

Is it still valid?

Member

jdm commented Oct 7, 2017

This can be dealt with separately in the smallvec repository if it's still a real issue (which sounds implausible after this much time).

jdm closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment