Bug#871638: [Pkg-rust-maintainers] Bug#871638: Bug#871638: rustc panics when trying to list the target cpus if the current directory does not exist anymore

2017-11-01 Thread Laurent Arnoud 
Hi all,

This is reported and merged in https://github.com/rust-lang/rust/pull/45505

Cheers,

-- 
Laurent


signature.asc
Description: PGP signature

Bug#871638: [Pkg-rust-maintainers] Bug#871638: Bug#871638: rustc panics when trying to list the target cpus if the current directory does not exist anymore

2017-08-10 Thread Ximin Luo 
Control: severity -1 minor

Markus Wanner:
> Control: tags -1 +confirmed
> Control: found -1 1.18.0+dfsg1
> 
> Hello Alex,
> 
> On 08/10/2017 10:32 AM, Alex Riesen wrote:
>> just trying to run the commands below (with or without RUST_BACKTRACE) causes
>> rustc to panic. The removal of the directory was originally not intentional,
>> so a crash for such harmless command was a bit of surprise.
> 
> thanks for your bug report, I can confirm this issue even with the
> current version of rustc (in sid).
> 
> Note that with a current nightly (rustc 1.21.0-nightly (cbbe17aa7
> 2017-08-07)) obtained via rustup, I instead get the following error:
> 
> error: couldn't find value of CARGO_HOME
> info: caused by: No such file or directory (os error 2)
> 

Hi all, thanks for the bug report and confirmation.

I'd be very surprised if this was a Debian-specific problem, therefore I 
encourage you to file this issue upstream here:

https://github.com/rust-lang/rust/issues/

More people are looking at that than this Debian bugs page, and I need to spend 
my own time wisely to deal with other parts of the rust Debian packaging, and 
am unlikely to be able to deal with this one properly. Sorry about that.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#871638: [Pkg-rust-maintainers] Bug#871638: rustc panics when trying to list the target cpus if the current directory does not exist anymore

2017-08-10 Thread Markus Wanner 
Control: tags -1 +confirmed
Control: found -1 1.18.0+dfsg1

Hello Alex,

On 08/10/2017 10:32 AM, Alex Riesen wrote:
> just trying to run the commands below (with or without RUST_BACKTRACE) causes
> rustc to panic. The removal of the directory was originally not intentional,
> so a crash for such harmless command was a bit of surprise.

thanks for your bug report, I can confirm this issue even with the
current version of rustc (in sid).

Note that with a current nightly (rustc 1.21.0-nightly (cbbe17aa7
2017-08-07)) obtained via rustup, I instead get the following error:

error: couldn't find value of CARGO_HOME
info: caused by: No such file or directory (os error 2)

Kind Regards

Markus Wanner



signature.asc
Description: OpenPGP digital signature

Bug#871638: rustc panics when trying to list the target cpus if the current directory does not exist anymore

2017-08-10 Thread Alex Riesen 
Package: rustc
Version: 1.14.0+dfsg1-3
Severity: normal

Dear Maintainer,

just trying to run the commands below (with or without RUST_BACKTRACE) causes
rustc to panic. The removal of the directory was originally not intentional,
so a crash for such harmless command was a bit of surprise.

$ mkdir dir
$ cd dir
$ rm -rf ../dir
$ RUST_BACKTRACE=1 rustc -C target-cpu=help
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 `Result::unwrap()` on an `Err` value: Error 
{ repr: Os { code: 2, message: "No such file or directory" } }', 
src/libcore/result.rs:837
stack backtrace:
   1: 0x7f7d23970dda - 
   2: 0x7f7d2398305f - 
   3: 0x7f7d2397f8a5 - 
   4: 0x7f7d2397ffc7 - 
std::panicking::rust_panic_with_hook::h109e116a3a861224
   5: 0x7f7d2397fe54 - 
   6: 0x7f7d2397fd79 - std::panicking::begin_panic_fmt::h26713cea9bce3ab0
   7: 0x7f7d2397fd07 - rust_begin_unwind
   8: 0x7f7d239cb41d - core::panicking::panic_fmt::hcfbb59eeb7f27f75
   9: 0x7f7d20be63d3 - 
  10: 0x7f7d20d6ebcc - rustc::session::build_session_::h7a3559f2373a5d05
  11: 0x7f7d20d6dd7e - 
rustc::session::build_session_with_codemap::h68bc7bcd2f34eee4
  12: 0x7f7d20d6d72c - rustc::session::build_session::h437fda3c327a8bde
  13: 0x7f7d23d26030 - >::no_input::h8047df7741757d1c
  14: 0x7f7d23d21d27 - rustc_driver::run_compiler::hafe7bbfedf95a825
  15: 0x7f7d23c57378 - 
  16: 0x7f7d2398ae0a - __rust_maybe_catch_panic
  17: 0x7f7d23c76fa8 - 
  18: 0x7f7d2397eb74 - 
  19: 0x7f7d1ed4f493 - start_thread
  20: 0x7f7d23645afe - __clone
  21:0x0 - 

Sadly, the backtrace is not improved by install the debug symbols.

-- System Information:
Debian Release: 9.1
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.4 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages rustc depends on:
ii  binutils  2.28-5
ii  gcc   4:6.3.0-4
ii  libc6 2.24-11+deb9u1
ii  libc6-dev [libc-dev]  2.24-11+deb9u1
ii  libjs-jquery  3.1.1-2
ii  libstd-rust-dev   1.14.0+dfsg1-3

Versions of packages rustc recommends:
ii  rust-gdb   1.14.0+dfsg1-3
ii  rust-lldb  1.14.0+dfsg1-3

Versions of packages rustc suggests:
ii  rust-doc  1.14.0+dfsg1-3

-- no debconf information

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus