rust-lang / rust-lang/rust

cargo build crash

Open
#122,384 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-bug I-ICE S-needs-repro T-compiler
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Code
use env_file_reader::read_file;
use ormlite::model::*;

fn main() {
    let env_variables = read_file(".env");
    let mut db_conn = ormlite::postgres::PgConnection(&env_variables["DATABASE_URL"]).await.unwrap();

    println!("Hello, world!");
}
Meta

rustc --version --verbose:

<version>
Error output
3149:     0x7ffd3813393d - <unknown>
3150:     0x7ffd38093f27 - <unknown>
3151:     0x7ffd38101a15 - <unknown>
3152:     0x7ffd36edddb2 - <unknown>
3153:     0x7ffd3816e9f8 - <unknown>
3154:     0x7ffd38be60a9 - <unknown>
3155:     0x7ffd38be5c96 - <unknown>
3156:     0x7ffdffa6715b - ChangeTimerQueueTimer
3157:     0x7ffe02297c54 - RtlUserFiberStart

error: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

note: rustc 1.76.0 (07dca489a 2024-02-04) running on x86_64-pc-windows-msvc

note: compiler flags: --crate-type bin -C embed-bitcode=no -C debuginfo=2 -C incremental=[REDACTED]

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
thread panicked while processing panic. aborting.
error: could not compile `rfidcontroller` (bin "rfidcontroller")
Backtrace

<backtrace>
`Caused by:
  process didn't exit successfully: `rustc --crate-name rfidcontroller --edition=2021 src\main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=211 --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=0af02bceaec6d635 --out-dir C:\Users\bstro\source\repos\rfidcontroller\target\debug\deps -C incremental=C:\Users\bstro\source\repos\rfidcontroller\target\debug\incremental -L dependency=C:\Users\bstro\source\repos\rfidcontroller\target\debug\deps --extern chrono=C:\Users\bstro\source\repos\rfidcontroller\target\debug\deps\libchrono-6298c5256a83f489.rlib --extern env_file_reader=C:\Users\bstro\source\repos\rfidcontroller\target\debug\deps\libenv_file_reader-697916ab711f75b4.rlib --extern ormlite=C:\Users\bstro\source\repos\rfidcontroller\target\debug\deps\libormlite-ba21f06120e8471e.rlib -L native=C:\Users\bstro\.cargo\registry\src\index.crates.io-6f17d22bba15001f\windows_x86_64_msvc-0.52.4\lib -L native=C:\Users\bstro\.cargo\registry\src\index.crates.io-6f17d22bba15001f\windows_x86_64_msvc-0.48.5\lib -L native=C:\Users\bstro\source\repos\rfidcontroller\target\debug\build\ring-b41cbf2e56a7315d\out` (exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied src\main.rs reproducer and run cargo build on the reported Windows target using the given Rust toolchain details. Recheck the example with RUST_BACKTRACE=1 and compare stable, beta, or nightly as suggested by the report. Done means producing a minimal reproducible case with complete version and backtrace information, or identifying a confirmed compiler failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.