Skip to content

Native tasks also want to know the stack bounds #11293

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
brson opened this issue Jan 3, 2014 · 0 comments · Fixed by #11306
Closed

Native tasks also want to know the stack bounds #11293

brson opened this issue Jan 3, 2014 · 0 comments · Fixed by #11306
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@brson
Copy link
Contributor

brson commented Jan 3, 2014

Servo currently wants to run spidermonkey on native tasks and spidermonkey needs to know the bounds of the stack, but this information isn't conveniently available to native tasks.
@alexcrichton alexcrichton mentioned this issue Jan 4, 2014
Merged
bors added a commit that referenced this issue Jan 4, 2014
@bors
auto merge of #11306 : alexcrichton/rust/native-bounds, r=pcwalton
b432e82 
This allows inspection of the current task's bounds regardless of what the
underlying task is.

Closes #11293
flip1995 pushed a commit to flip1995/rust that referenced this issue Jul 11, 2024
@bors
Auto merge of rust-lang#11293 - mrnossiom:11234, r=Jarcho
94a000b 
feat: add cfg_not_test lint

<!--
- \[x] Followed [lint naming conventions][lint_naming]
- \[x] Added passing UI tests (including committed `.stderr` file)
- \[x] `cargo test` passes locally
- \[x] Executed `cargo dev update_lints`
- \[ ] Added lint documentation
- \[x] Run `cargo dev fmt`

[lint_naming]: https://rust-lang.github.io/rfcs/0344-conventions-galore.html#lints
-->

Fixes rust-lang#11234

changelog: new lint: [`cfg_not_test`]

I don't know whether to lint only the `attr` or also the item associated to it. I guess this would mean putting the check in another place than `check_attribute` but I can't find a way to get the associated item to the attribute.

Also, I'm not sure how to document this lint, I feel like my explications are bad.
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

Successfully merging a pull request may close this issue.

Add a stack_bounds function to the Runtime trait alexcrichton/rust
1 participant
@brson