-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Leaks when failures occur during unwinding #1482
Comments
@bblum - is this still an issue after your work on failure? |
To be honest, I'm not sure. I closed #1078 with some pretty easy code reorganisation, and the referred test case magically seems to work fine. |
Then I'm going to close this. If it becomes an issue again, it should be pretty obvious. |
Won't complain, but I'm worried we just might not have a test case. @nikomatsakis can you input? |
Well, I'm of the philosophy that "if there's no test case, there's no bug" :-) |
I am not sure what I meant about that testcase from #1078, it doesn't seem to fail during unwinding. Well, I recall that it could fail sometimes when invoking
Something like that would seem to be the test for this bug. For me at least, this test passes right now. |
* Add sample CodeLLDB launch.json There is a section with [instructions for setting up source analyzer in VSCode](https://rustc-dev-guide.rust-lang.org/building/suggested.html#configuring-rust-analyzer-for-rustc), but nothing for setting up debugging with CodeLLDB. This adds a sample configuration that may not be ideal, but appears to work for me. To source highlight the snippet, uses JavaScript instead of JSON so that comments do not show up as errors highlighted in red (VSCode allows comments). * Update src/compiler-debugging.md Co-authored-by: jyn <github@jyn.dev> * Update src/compiler-debugging.md Co-authored-by: jyn <github@jyn.dev> --------- Co-authored-by: Santiago Pastorino <spastorino@gmail.com> Co-authored-by: jyn <github@jyn.dev>
* Add sample CodeLLDB launch.json There is a section with [instructions for setting up source analyzer in VSCode](https://rustc-dev-guide.rust-lang.org/building/suggested.html#configuring-rust-analyzer-for-rustc), but nothing for setting up debugging with CodeLLDB. This adds a sample configuration that may not be ideal, but appears to work for me. To source highlight the snippet, uses JavaScript instead of JSON so that comments do not show up as errors highlighted in red (VSCode allows comments). * Update src/compiler-debugging.md Co-authored-by: jyn <github@jyn.dev> * Update src/compiler-debugging.md Co-authored-by: jyn <github@jyn.dev> --------- Co-authored-by: Santiago Pastorino <spastorino@gmail.com> Co-authored-by: jyn <github@jyn.dev>
If a failure occurs during unwinding or executing a resource, we potentially leak. This is blocking #1078 (which also includes a reference to a testcase).
The text was updated successfully, but these errors were encountered: