Bug#918854: [Pkg-rust-maintainers] Bug#918854: Bug#918854: segfault updating crates.io index

2019-05-18 Thread Ximin Luo
Control: tags -1 - moreinfo unreproducible Control: affects -1 + cargo -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

Bug#918854: [Pkg-rust-maintainers] Bug#918854: segfault updating crates.io index

2019-05-18 Thread Ximin Luo
Control: reassign -1 libgit2 0.27.7+dfsg.1-0.1 I figured out the problem and have a bug fix on the way. The problem is in libgit2 not cargo. Actually libgit2 has a shit ton of holes. The fix for this particular bug is cherry-picked from here: https://github.com/libgit2/libgit2/commits/master/s

Bug#918854: segfault updating crates.io index

2019-05-16 Thread Antoine Beaupre
Package: cargo Version: 0.33.0-1 Followup-For: Bug #918854 I'm seeing the same thing in buster right now. It's intermittent, and the build eventually finishes if retried. It's especially annoying when building Docker containers, which do not afford the luxury of retries. A reliable way to trigger

Bug#918854: [Pkg-rust-maintainers] Bug#918854: segfault updating crates.io index

2019-04-27 Thread Горбешко Богдан
On 27.04.2019 20:33, Ximin Luo wrote: Горбешко Богдан: I get almost the same, with no proxies: Sorry for late reply, I missed your messages back in March. I still can't reproduce this on my end, so I won't be able to fix the problem. Can you try to collect more information? - does the failu

Bug#918854: [Pkg-rust-maintainers] Bug#918854: segfault updating crates.io index

2019-04-27 Thread Ximin Luo
Горбешко Богдан: > I get almost the same, with no proxies: > Sorry for late reply, I missed your messages back in March. I still can't reproduce this on my end, so I won't be able to fix the problem. Can you try to collect more information? - does the failure still occur with a fresh .cargo? (

Bug#918854: segfault updating crates.io index

2019-04-27 Thread Горбешко Богдан
I get almost the same, with no proxies: #0  __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120 #1  0x55be142a in std::ffi::c_str::CStr::from_ptr () #2  0x55ae8013 in git2::transport::subtransport_action::{{closure}} ()     at /usr/share/cargo/registry/cargo-0.33.0/v

Bug#918854: [Pkg-rust-maintainers] Bug#918854: Bug#918854: segfault updating crates.io index

2019-03-05 Thread Josh Triplett
On Sun, Jan 20, 2019 at 07:19:00AM +, Ximin Luo wrote: > I can't reproduce this, can you install cargo-dbgsym rustc-dbgsym rust-gdb > libstd-rust-1.31-dbgsym libllvm7-dbgsym libc6-dbg and provide a backtrace? I can reliably reproduce this, and I think I've figured out the distinguishing facto

Bug#918854: segfault updating crates.io index

2019-03-05 Thread Горбешко Богдан
Confirming this in 1.32.0.

Bug#918854: [Pkg-rust-maintainers] Bug#918854: segfault updating crates.io index

2019-01-19 Thread Ximin Luo
Control: severity -1 important Control: tag -1 + moreinfo unreproducible I can't reproduce this, can you install cargo-dbgsym rustc-dbgsym rust-gdb libstd-rust-1.31-dbgsym libllvm7-dbgsym libc6-dbg and provide a backtrace? X Josh Triplett: > Package: cargo > Version: 0.31.1-1 > Severity: grave

Bug#918854: segfault updating crates.io index

2019-01-09 Thread Josh Triplett
Package: cargo Version: 0.31.1-1 Severity: grave Any time I try to update the crates.io index with the currently packaged version of cargo, I get a segfault: $ cargo update Updating crates.io index Segmentation fault I can reproduce this in a brand new project (`cargo new foo`) by adding any