Closed
Description
$ rustc --version
rustc 1.29.2 (17a9dc751 2018-10-05)
$ cargo clippy -V
0.0.212
Line-wrapped output (for viewing convenience; irrelevant path specs replaced with ...
). [In real life, the "Caused by" lines are one long line all the way through the end of the SIGSEGV.]
error: Could not compile `byte-tools`.
Caused by:
process didn't exit successfully: `/usr/local/bin/clippy-driver rustc --crate-name
byte_tools .../.cargo/registry/src/github.com-1ecc6299db9ec823/byte-tools-0.2.0/src/lib.rs
--crate-type lib --emit=dep-info,metadata -C debuginfo=2 -C metadata=5da25c9bb6e69df5 -C
extra-filename=-5da25c9bb6e69df5 --out-dir .../target/debug/deps -L
dependency=.../target/debug/deps --cap-lints allow`
(signal: 11, SIGSEGV: invalid memory reference)
error: Could not compile `byteorder`.
Caused by:
process didn't exit successfully: `/usr/local/bin/clippy-driver rustc --crate-name
byteorder .../.cargo/registry/src/github.com-1ecc6299db9ec823/byteorder-1.2.4/src/lib.rs
--crate-type lib --emit=dep-info,metadata -C debuginfo=2 --cfg 'feature="default"' --cfg
'feature="std"' -C metadata=9166e152500d52e7 -C extra-filename=-9166e152500d52e7 --out-dir
.../target/debug/deps -L dependency=.../target/debug/deps --cap-lints allow`
(signal: 11, SIGSEGV: invalid memory reference)
This is reproducible. It happens regardless of the status of cargo clean
; i.e., if I do issue cargo clean; cargo clippy
it happens, and if I do cargo build; cargo clippy
it happens. (Note that my build succeeds).
Please let me know if you need any additional information.