Skip to content

Various doc fixes #11477

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.

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

Merged
merged 2 commits into from
Jan 12, 2014
Merged

Various doc fixes #11477

merged 2 commits into from
Jan 12, 2014

Conversation

adrientetar
Copy link
Contributor

Mostly cleanups for doc and READMEs. Fixes the bug reporting link.

# What does it mean when a program exits with `leaked memory in rust main loop (2 objects)' failed, rt/memory_region.cpp:99 2 objects`?
# What does it mean when a program exits with `leaked memory`?

The error looks like this: `leaked memory in rust main loop (2 objects)' failed, rt/memory_region.cpp:99 2 objects`.

This message indicates a memory leak, and is mostly likely to happen on rarely exercised failure paths. Note that failure unwinding is not yet implemented on windows so this is expected. If you see this on Linux or Mac it's a compiler bug; please report it.

# Why do gdb backtraces end with the error 'previous frame inner to this frame (corrupt stack?)'?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

those whole entry can be removed, segmented stacks are gone.

bors added a commit that referenced this pull request Jan 11, 2014
Mostly cleanups for doc and READMEs. Fixes the bug reporting link.
@bors bors closed this Jan 12, 2014
@bors bors merged commit 7279409 into rust-lang:master Jan 12, 2014
@adrientetar adrientetar deleted the bug-report branch January 12, 2014 09:21
flip1995 pushed a commit to flip1995/rust that referenced this pull request Sep 12, 2023
Auto deref does not apply on union field

changelog: [`explicit_auto_deref`]: do not suggest propose to auto-dereference an union field

Fix rust-lang#11474
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants