kani icon indicating copy to clipboard operation
kani copied to clipboard

--debug doesn't work anymore

Open tedinski opened this issue 3 years ago • 1 comments

$ cargo kani --debug --verbose
KANIFLAGS="--goto-c --log-level=debug --assertion-reach-checks -C symbol-mangling-version=v0" RUSTC="/home/ubuntu/rmc/target/debug/kani-compiler" RUSTFLAGS="--kani-flags" cargo build --target x86_64-unknown-linux-gnu --target-dir target -v
error: output of --print=file-names has changed in the compiler, cannot parse
command was: `/home/ubuntu/rmc/target/debug/kani-compiler - --crate-name ___ --print=file-names --kani-flags --target x86_64-unknown-linux-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg`

--- stdout
DEBUG kani_compiler Sysroot path., path="/home/ubuntu/.rustup/toolchains/nightly-2022-06-09-x86_64-unknown-linux-gnu", sysroot_arg=None
DEBUG kani_compiler Compile, rustc_args=["rustc", "-C", "overflow-checks=on", "-C", "panic=abort", "-Z", "unstable-options", "-Z", "panic_abort_tests=yes", "-Z", "trim-diagnostic-paths=no", "-Z", "human_readable_cgu_names", "--cfg=kani", "-Z", "crate-attr=feature(register_tool)", "-Z", "crate-attr=register_tool(kanitool)", "-L", "/home/ubuntu/rmc/target/debug/build/kani-compiler-28743720f584101a/out/lib", "--extern", "kani", "--extern", "noprelude:std=/home/ubuntu/rmc/target/debug/build/kani-compiler-28743720f584101a/out/lib/libstd.rlib", "-C", "symbol-mangling-version=v0", "-", "--crate-name", "___", "--print=file-names", "--target", "x86_64-unknown-linux-gnu", "--crate-type", "bin", "--crate-type", "rlib", "--crate-type", "dylib", "--crate-type", "cdylib", "--crate-type", "staticlib", "--crate-type", "proc-macro", "--print=sysroot", "--print=cfg", "--sysroot", "/home/ubuntu/.rustup/toolchains/nightly-2022-06-09-x86_64-unknown-linux-gnu"]
___
lib___.rlib
lib___.so
lib___.so
lib___.a
lib___.so
/home/ubuntu/.rustup/toolchains/nightly-2022-06-09-x86_64-unknown-linux-gnu
debug_assertions
kani
panic="abort"
proc_macro
target_abi=""
target_arch="x86_64"
target_endian="little"
target_env="gnu"
target_family="unix"
target_has_atomic="16"
target_has_atomic="32"
target_has_atomic="64"
target_has_atomic="8"
target_has_atomic="ptr"
target_has_atomic_equal_alignment="16"
target_has_atomic_equal_alignment="32"
target_has_atomic_equal_alignment="64"
target_has_atomic_equal_alignment="8"
target_has_atomic_equal_alignment="ptr"
target_has_atomic_load_store="16"
target_has_atomic_load_store="32"
target_has_atomic_load_store="64"
target_has_atomic_load_store="8"
target_has_atomic_load_store="ptr"
target_os="linux"
target_pointer_width="64"
target_thread_local
target_vendor="unknown"
unix

Error: cargo exited with status exit status: 101

tedinski avatar Jul 07 '22 19:07 tedinski

A workaround that worked for me: run kani first without --debug and then again with --debug.

fzaiser avatar Jul 26 '22 20:07 fzaiser