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.

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

Error installing cargo-watch #135913

Open
Aditya190600 opened this issue Jan 23, 2025 · 3 comments
Open

Error installing cargo-watch #135913

Aditya190600 opened this issue Jan 23, 2025 · 3 comments
Labels
C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ S-needs-repro Status: This issue has no reproduction and needs a reproduction to make progress. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@Aditya190600
Copy link

Code

cargo install cargo-watch

Meta

rustc --version --verbose:

rustc 1.84.0 (9fc6b4312 2025-01-07)
binary: rustc
commit-hash: 9fc6b43126469e3858e2fe86cafb4f0fd5068869
commit-date: 2025-01-07
host: x86_64-unknown-linux-gnu
release: 1.84.0
LLVM version: 19.1.5

Error output

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.84.0 (9fc6b4312 2025-01-07) running on x86_64-unknown-linux-gnu

note: compiler flags: --crate-type lib -C opt-level=3 -C panic=abort -C linker-plugin-lto -C codegen-units=1 -C strip=debuginfo

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


thread 'main' panicked at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869/library/std/src/thread/mod.rs:1719:40:
called `Option::unwrap()` on a `None` value
stack backtrace:
   Compiling inotify v0.7.1
   0:     0x7148abd8682a - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::ha4a311b32f6b4ad8
   1:     0x7148ac4277e2 - core::fmt::write::h1866771663f62b81
   2:     0x7148ad281d51 - std::io::Write::write_fmt::hb549e7444823135e
   3:     0x7148abd86682 - std::sys::backtrace::BacktraceLock::print::hddd3a9918ce29aa7
   4:     0x7148abd88b5a - std::panicking::default_hook::{{closure}}::h791f75256b902d7d
   5:     0x7148abd889c0 - std::panicking::default_hook::h82cc572fcb0d8cd7
   6:     0x7148aae14f55 - std[1b49f43dde054edc]::panicking::update_hook::<alloc[f0e0d4128a1437e6]::boxed::Box<rustc_driver_impl[c421ed190efad9be]::install_ice_hook::{closure#0}>>::{closure#0}
   7:     0x7148abd89238 - std::panicking::rust_panic_with_hook::he21644cc2707f2c4
   8:     0x7148abd88fd6 - std::panicking::begin_panic_handler::{{closure}}::h42f7c414fed3cad9
   9:     0x7148abd86cd9 - std::sys::backtrace::__rust_end_short_backtrace::ha26cf5766b4e8c65
  10:     0x7148abd88ccc - rust_begin_unwind
  11:     0x7148a88e43f0 - core::panicking::panic_fmt::h74866b78e934b1c0
  12:     0x7148a8afe56c - core::panicking::panic::h95d8269cf8bd4f7a
  13:     0x7148a9e65909 - core::option::unwrap_failed::hca433a9693b91bd2
  14:     0x7148ad27a0d9 - rustc_driver_impl[c421ed190efad9be]::run_compiler
  15:     0x7148ad1c99e0 - rustc_driver_impl[c421ed190efad9be]::main
  16:     0x5eadf5e9e497 - rustc_main[302bc4b73869fe48]::main
  17:     0x5eadf5e9e483 - std[1b49f43dde054edc]::sys::backtrace::__rust_begin_short_backtrace::<fn(), ()>
  18:     0x5eadf5e9e479 - std[1b49f43dde054edc]::rt::lang_start::<()>::{closure#0}
  19:     0x7148ad29dd41 - std::rt::lang_start_internal::h78dd36c15a6b42b8
  20:     0x5eadf5ea5ea7 - main
  21:     0x7148a7429d90 - <unknown>
  22:     0x7148a7429e40 - __libc_start_main
  23:     0x5eadf5ea5db6 - <unknown>
  24:                0x0 - <unknown>

   Compiling clap v2.34.0


@Aditya190600 Aditya190600 added C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jan 23, 2025
@rustbot rustbot added the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label Jan 23, 2025
@saethlin
Copy link
Member

saethlin commented Jan 23, 2025

That is weird... If you try to run cargo install cargo-watch again, do you get the same crash?

I've tried cargo +stable install cargo-watch as you did and it does not crash for me.

@saethlin saethlin added S-needs-repro Status: This issue has no reproduction and needs a reproduction to make progress. and removed needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. labels Jan 23, 2025
@theemathas
Copy link
Contributor

theemathas commented Jan 23, 2025

Possibly relevant: #124466 and #112521

@ChrisDenton
Copy link
Member

Yes, this is the sort of error I'd expect if the thread was forcibly terminated. However, I'm not sure why that would happen in this case.

Is there any security or sandboxing features that could be involved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ S-needs-repro Status: This issue has no reproduction and needs a reproduction to make progress. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

5 participants