Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upValgrind failure during unwinding in trans #19481
Comments
nikomatsakis
added a commit
to nikomatsakis/rust
that referenced
this issue
Dec 3, 2014
This comment has been minimized.
This comment has been minimized.
|
Commit is 931758c |
This comment has been minimized.
This comment has been minimized.
|
Sounds like a lurking soundness issue. Nominating to revisit this. |
kmcallister
added
the
I-nominated
label
Jan 19, 2015
This comment has been minimized.
This comment has been minimized.
|
P-low, not 1.0. |
pnkfelix
added
P-low
P-medium
and removed
I-nominated
P-low
labels
Jan 22, 2015
This comment has been minimized.
This comment has been minimized.
|
(niko pushed for P-high instead) |
This comment has been minimized.
This comment has been minimized.
|
What's the action item here? Revert the fixme commit and run |
brson
closed this
Aug 4, 2016
This comment has been minimized.
This comment has been minimized.
|
Old issue, lots of changes since. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
nikomatsakis commentedDec 3, 2014
I ran into a mysterious valgrind issue that I didn't have time to pin down. The problem seems to be involved with the handoff of ownership from caller to callee; valgrind reports reads of freed memory, basically. There is a "FIXME" commit that converts a fn that took
Vec<T>to&[T], avoiding the problem (in this particular case, taking aVec<T>was a bit silly anyhow).