Skip to content
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

Valgrind doesn't understand writing arguments to another stack #1004

Closed
pcwalton opened this issue Oct 5, 2011 · 2 comments
Closed

Valgrind doesn't understand writing arguments to another stack #1004

pcwalton opened this issue Oct 5, 2011 · 2 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@pcwalton
Copy link
Contributor

pcwalton commented Oct 5, 2011

We write arguments from the Rust stack to the C stack when doing stack switching. This confuses Valgrind, which thinks that it's a mistake. We need to work around this somehow.
@brson
Copy link
Contributor

brson commented Oct 12, 2011

Is this resolved?

@brson
Copy link
Contributor

brson commented Mar 6, 2012

Yes.

@brson brson closed this as completed Mar 6, 2012
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
@tgymnich
fix llvm 14/15 build (rust-lang#1004)
3e1e2d0
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@adpaco-aws @tedinski
Documentation: Updates for "First steps" (rust-lang#1004)
f37dea0 
* Documentation: Updates for "First steps"

* Use "preferred" instead of "favorite"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brson @pcwalton