Skip to content

ICE when using placement new with non arena types #2854

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

Closed
msullivan opened this issue Jul 9, 2012 · 1 comment
Closed

ICE when using placement new with non arena types #2854

msullivan opened this issue Jul 9, 2012 · 1 comment
Labels
A-type-system Area: Type system I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.

Comments

@msullivan
Copy link
Contributor

When code tries to use placement new with type that doesn't implement the proper arena methods, after printing out a reasonable diagnostic, rustc ICEs:

fn main() {
    new (7) 43;
}

produces

nubs/bogus_arena.rs:2:4: 2:15 error: no `alloc()` method found for type `<VI0>`
nubs/bogus_arena.rs:2     new (7) 43;
                          ^~~~~~~~~~~
error: internal compiler error: no type for node 4: unknown node (id=4) in fcx 7fed8813ecc0
@msullivan
Copy link
Contributor Author

placement new is gone. Closing.

RalfJung pushed a commit to RalfJung/rust that referenced this issue Apr 28, 2023
Hide backtrace from stderr files

fixes rust-lang#2853

seems not very important to test in this detail. I could try to keep a few lines at the start around so we know what's going on (they should be fairly reliable)
RalfJung pushed a commit to RalfJung/rust that referenced this issue Apr 30, 2023
Hide backtrace from stderr files

fixes rust-lang#2853

seems not very important to test in this detail. I could try to keep a few lines at the start around so we know what's going on (they should be fairly reliable)
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
Output the tagged version in the `versioning` step of the release
workflow to avoid a failure in the posterior docker build step (see
rust-lang#2851 for more details).

This has been tested in my fork, where:
1. Pushing the `kani-0.40.0` without any changes generated the same
failure [in this
run](https://github.com/adpaco-aws/rmc/actions/runs/6738081085/job/18317679294)
2. Committing the change in this PR and pushing the `kani-0.40.0` again
resulted in a successful build [in this
run](https://github.com/adpaco-aws/rmc/actions/runs/6738159804/job/18317924214)
3. The tagged image can be downloaded from my fork, as seen
[here](https://github.com/adpaco-aws/rmc/pkgs/container/kani-ubuntu-20.04).

Resolves rust-lang#2851
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-type-system Area: Type system I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
Projects
None yet
Development

No branches or pull requests

1 participant