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

Move the fail upcall to core::rt for better debugging #3259

Closed
brson opened this issue Aug 23, 2012 · 1 comment
Closed

Move the fail upcall to core::rt for better debugging #3259

brson opened this issue Aug 23, 2012 · 1 comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Aug 23, 2012

On lesser platforms like windows we can't backtrace through __morestack in gdb, so finding the cause of a failure is hard. if we could break before switching stacks then we could see the entire backtrace.
@brson
Copy link
Contributor Author

brson commented Aug 23, 2012

This is already done, dummy.

@brson brson closed this as completed Aug 23, 2012
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
@topecongiro
Fix shape when formatting return or break expr on statement position (r…
996d5e8 
…ust-lang#3259)
RalfJung pushed a commit to RalfJung/rust that referenced this issue Jan 7, 2024
@bors
Auto merge of rust-lang#3259 - RalfJung:jemalloc, r=RalfJung
d93ca6e 
use jemalloc as global allocator

Hopefully fixes rust-lang/miri#3255
jaisnan pushed a commit to jaisnan/rust-dev that referenced this issue Jul 29, 2024
@celinval
Fix contract of constant fn with effect feature (rust-lang#3259)
34b35d8 
We now check if the host effect index is present. If so, remove it
before performing stub operation.

Resolves rust-lang#3258
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brson