cargo build && cargo check cause "the compiler unexpectedly panicked" #40755

seb-odessa · 2017-03-23T10:54:05Z

How I faced it:
$ rustup update
$ cargo new sqlite_demo --bin
Created binary (application) sqlite_demo project
rust$ rustc --version
rustc 1.16.0 (30cf806 2017-03-10)
$ cd sqlite_demo/

Add rusqlite dependency into Cargo.toml:

[package]
name = "sqlite_demo"
version = "0.1.0"
authors = ["..."]

[dependencies]
    rusqlite = "*"  <-- this one was added

$ cargo build

Blocking waiting for file lock on the registry index
Updating registry `https://github.com/rust-lang/crates.io-index`
Blocking waiting for file lock on rusqlite-0.10.1.crate

Downloading libsqlite3-sys v0.7.1
Downloading lru-cache v0.1.0
Downloading time v0.1.36
Downloading pkg-config v0.3.9
Downloading linked-hash-map v0.2.1
Blocking waiting for file lock on libc-0.2.21.crate
Compiling libc v0.2.21
Compiling time v0.1.36
Compiling bitflags v0.7.0
Compiling linked-hash-map v0.2.1
Compiling lru-cache v0.1.0
Compiling pkg-config v0.3.9
Compiling libsqlite3-sys v0.7.1
Compiling rusqlite v0.10.1
Compiling sqlite_demo v0.1.0 (file:///home/seb/workspace/rust/sqlite_demo)
Finished dev [unoptimized + debuginfo] target(s) in 47.84 secs

copy/paste content of main.rs from the demo (http://jgallagher.github.io/rusqlite/rusqlite/index.html):

extern crate rusqlite;
extern crate time;

use time::Timespec;
use rusqlite::Connection;

#[derive(Debug)]
struct Person {
    id: i32,
    name: String,
    time_created: Timespec,
    data: Option<Vec<u8>>
}

fn main() {
    let conn = Connection::open_in_memory().unwrap();

    conn.execute("CREATE TABLE person (
                  id              INTEGER PRIMARY KEY,
                  name            TEXT NOT NULL,
                  time_created    TEXT NOT NULL,
                  data            BLOB
                  )", &[]).unwrap();
    let me = Person {
        id: 0,
        name: "Steven".to_string(),
        time_created: time::get_time(),
        data: None
    };
    conn.execute("INSERT INTO person (name, time_created, data)
                  VALUES (?1, ?2, ?3)",
                 &[&me.name, &me.time_created, &me.data]).unwrap();

    let mut stmt = conn.prepare("SELECT id, name, time_created, data FROM person").unwrap();
    let person_iter = stmt.query_map(&[], |row| {
        Person {
            id: row.get(0),
            name: row.get(1),
            time_created: row.get(2),
            data: row.get(3)
        }
    }).unwrap();

    for person in person_iter {
        println!("Found person {:?}", person.unwrap());
    }
}

$ cargo check
Compiling bitflags v0.7.0
Compiling linked-hash-map v0.2.1
Compiling lru-cache v0.1.0
Compiling libc v0.2.21
Compiling time v0.1.36
Compiling libsqlite3-sys v0.7.1
Compiling rusqlite v0.10.1
Compiling sqlite_demo v0.1.0 (file:///home/seb/workspace/rust/sqlite_demo)
error: internal compiler error: unexpected panic

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

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

thread 'rustc' panicked at 'called Option::unwrap() on a None value', /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/option.rs:323
note: Run with RUST_BACKTRACE=1 for a backtrace.

error: Could not compile sqlite_demo.

To learn more, run the command again with --verbose.

$ rustc --version --verbose
rustc 1.16.0 (30cf806 2017-03-10)
binary: rustc
commit-hash: 30cf806
commit-date: 2017-03-10
host: x86_64-unknown-linux-gnu
release: 1.16.0
LLVM version: 3.9

The text was updated successfully, but these errors were encountered:

seb-odessa · 2017-03-23T10:58:14Z

$ export RUST_BACKTRACE=1
$ cargo check --verbose

     Fresh bitflags v0.7.0
      Fresh pkg-config v0.3.9
      Fresh libsqlite3-sys v0.7.1
      Fresh libc v0.2.21
      Fresh time v0.1.36
      Fresh linked-hash-map v0.2.1
      Fresh lru-cache v0.1.0
      Fresh rusqlite v0.10.1
  Compiling sqlite_demo v0.1.0 (file:///home/seb/workspace/rust/sqlite_demo)
    Running `rustc --crate-name sqlite_demo src/main.rs --crate-type bin --emit=dep-info,metadata -C debuginfo=2 -C metadata=16738e1e120f8bd4 -C extra-filename=-16738e1e120f8bd4 --out-dir /home/seb/workspace/rust/sqlite_demo/target/debug/deps -L dependency=/home/seb/workspace/rust/sqlite_demo/target/debug/deps --extern rusqlite=/home/seb/workspace/rust/sqlite_demo/target/debug/deps/librusqlite-b593b251ea54768f.rmeta`
error: internal compiler error: unexpected panic

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

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: run with `RUST_BACKTRACE=1` for a backtrace

thread 'rustc' panicked at 'called `Option::unwrap()` on a `None` value', /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/option.rs:323
stack backtrace:
  1:     0x7f7cc99a640c - std::sys::imp::backtrace::tracing::imp::write::hf33ae72d0baa11ed
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:42
  2:     0x7f7cc99b49ae - std::panicking::default_hook::{{closure}}::h59672b733cc6a455
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:351
  3:     0x7f7cc99b4553 - std::panicking::default_hook::h1670459d2f3f8843
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:361
  4:     0x7f7cc99b4e4b - std::panicking::rust_panic_with_hook::hcf0ddb069e7beee7
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:555
  5:     0x7f7cc99b4ce4 - std::panicking::begin_panic::hd6eb68e27bdf6140
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:517
  6:     0x7f7cc99b4c09 - std::panicking::begin_panic_fmt::hfea5965948b877f8
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:501
  7:     0x7f7cc99b4b97 - rust_begin_unwind
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:477
  8:     0x7f7cc99f1edd - core::panicking::panic_fmt::hc0f6d7b2c300cdd9
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/panicking.rs:69
  9:     0x7f7cc99f1e14 - core::panicking::panic::h7abeb5b818ec354e
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/panicking.rs:49
 10:     0x7f7cc7675876 - rustc_metadata::creader::CrateLoader::resolve_crate::h6e72600e2dd6f65b
 11:     0x7f7cc767c98f - <rustc_metadata::creader::CrateLoader<'a> as rustc::middle::cstore::CrateLoader>::process_item::h3593d13570805f47
 12:     0x7f7cc6e9c8b0 - rustc_resolve::build_reduced_graph::<impl rustc_resolve::Resolver<'a>>::build_reduced_graph_for_item::h3cc2f08d7828c563
 13:     0x7f7cc6ea367f - <rustc_resolve::build_reduced_graph::BuildReducedGraphVisitor<'a, 'b> as syntax::visit::Visitor<'a>>::visit_item::h775ca4c5a23a8667
 14:     0x7f7cc6ea3b7f - <rustc_resolve::build_reduced_graph::BuildReducedGraphVisitor<'a, 'b> as syntax::visit::Visitor<'a>>::visit_item::h775ca4c5a23a8667
 15:     0x7f7cc6e975bf - rustc_resolve::macros::<impl syntax::ext::base::Resolver for rustc_resolve::Resolver<'a>>::visit_expansion::hc836a3e7268abdbf
 16:     0x7f7cc333577a - syntax::ext::expand::MacroExpander::collect_invocations::h32417ac98c0c9be1
 17:     0x7f7cc3334140 - syntax::ext::expand::MacroExpander::expand::h695353fd58aabfd3
 18:     0x7f7cc3333ba5 - syntax::ext::expand::MacroExpander::expand_crate::h9811866201c8237a
 19:     0x7f7cc9d410dc - rustc_driver::driver::phase_2_configure_and_expand::{{closure}}::h231d639b5d33e30c
 20:     0x7f7cc9d387f5 - rustc_driver::driver::phase_2_configure_and_expand::hd9965365e42d7a90
 21:     0x7f7cc9d3143a - rustc_driver::driver::compile_input::hd9f060ee16a643fb
 22:     0x7f7cc9d7d844 - rustc_driver::run_compiler::h762802568c0e140e
 23:     0x7f7cc9c89edb - std::panicking::try::do_call::h935e2f773deaf841
 24:     0x7f7cc99bdc8a - __rust_maybe_catch_panic
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libpanic_unwind/lib.rs:98
 25:     0x7f7cc9cb2112 - <F as alloc::boxed::FnBox<A>>::call_box::he43811d1f6894655
 26:     0x7f7cc99b3804 - std::sys::imp::thread::Thread::new::thread_start::he668872ac11287ba
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/liballoc/boxed.rs:624
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/sys_common/thread.rs:21
                       at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/sys/unix/thread.rs:84
 27:     0x7f7cc246d6b9 - start_thread
 28:     0x7f7cc966982c - clone
 29:                0x0 - <unknown>

error: Could not compile sqlite_demo.

Caused by:
process didn't exit successfully: rustc --crate-name sqlite_demo src/main.rs --crate-type bin --emit=dep-info,metadata -C debuginfo=2 -C metadata=16738e1e120f8bd4 -C extra-filename=-16738e1e120f8bd4 --out-dir /home/seb/workspace/rust/sqlite_demo/target/debug/deps -L dependency=/home/seb/workspace/rust/sqlite_demo/target/debug/deps --extern rusqlite=/home/seb/workspace/rust/sqlite_demo/target/debug/deps/librusqlite-b593b251ea54768f.rmeta (exit code: 101)

seb-odessa · 2017-03-23T12:52:24Z

The issue was resolved by adding absent time dependence into Cargo.toml and installing libsqlite3-dev:

$ cat Cargo.toml

[package]
name = "sqlite_demo"
version = "0.1.0"
authors = ["..."]

[dependencies]
    rusqlite = "*"
    time = "*"

$ sudo apt-get install libsqlite3-dev
$ cargo build
Compiling sqlite_demo v0.1.0 (file:///home/seb/workspace/rust/sqlite_demo)
Finished dev [unoptimized + debuginfo] target(s) in 1.64 secs

Aaron1011 · 2017-03-25T00:54:32Z

I'd like to work on this.

abonander · 2017-03-25T02:10:43Z

I believe this should have been fixed by #40542. Please try with a nightly newer than 2017-03-22 (when one is available) and let me know if it still happens.

Aaron1011 · 2017-03-25T13:35:39Z

You're right - it's fixed in the latest nightly.

dbrgn mentioned this issue Mar 23, 2017

Compiler panic when running 'cargo check' with missing crate #40757

Closed

steveklabnik added 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 Mar 23, 2017

TimNN mentioned this issue Apr 7, 2017

Compiler panicked while running cargo check #41144

Closed

mbrubeck closed this as completed Apr 21, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

cargo build && cargo check cause "the compiler unexpectedly panicked" #40755

cargo build && cargo check cause "the compiler unexpectedly panicked" #40755

seb-odessa commented Mar 23, 2017

seb-odessa commented Mar 23, 2017

seb-odessa commented Mar 23, 2017 •

edited

Loading

Aaron1011 commented Mar 25, 2017

abonander commented Mar 25, 2017 •

edited

Loading

Aaron1011 commented Mar 25, 2017

cargo build && cargo check cause "the compiler unexpectedly panicked" #40755

cargo build && cargo check cause "the compiler unexpectedly panicked" #40755

Comments

seb-odessa commented Mar 23, 2017

seb-odessa commented Mar 23, 2017

seb-odessa commented Mar 23, 2017 • edited Loading

Aaron1011 commented Mar 25, 2017

abonander commented Mar 25, 2017 • edited Loading

Aaron1011 commented Mar 25, 2017

seb-odessa commented Mar 23, 2017 •

edited

Loading

abonander commented Mar 25, 2017 •

edited

Loading