pijul_org / pijul

#16 Panic on record

Opened by ocharles, on March 22, 2017
Closed
ocharles commented on March 22, 2017
➜  quake-3-bsp-viewer RUST_LOG=info pijul record                                                               ~/work/quake-3-bsp-viewer
INFO:libpijul::record: now calling diff Key { patch: PatchId 0x3909b07691cfe986, line: LineId(0x0200000000000000) }
INFO:libpijul::graph: There are 3 SCC
INFO:libpijul::record: now calling diff Key { patch: PatchId 0x3909b07691cfe986, line: LineId(0x0500000000000000) }
INFO:libpijul::graph: There are 60 SCC
thread 'main' panicked at 'index 60 out of range for slice of length 59', src/libcore/slice.rs:560
note: Run with `RUST_BACKTRACE=1` for a backtrace.
➜  quake-3-bsp-viewer RUST_BACKTRACE=1 RUST_LOG=info pijul record                                              ~/work/quake-3-bsp-viewer
INFO:libpijul::record: now calling diff Key { patch: PatchId 0x3909b07691cfe986, line: LineId(0x0200000000000000) }
INFO:libpijul::graph: There are 3 SCC
INFO:libpijul::record: now calling diff Key { patch: PatchId 0x3909b07691cfe986, line: LineId(0x0500000000000000) }
INFO:libpijul::graph: There are 60 SCC
thread 'main' panicked at 'index 60 out of range for slice of length 59', src/libcore/slice.rs:560
stack backtrace:
   1:     0x560fde70d22a - std::sys::imp::backtrace::tracing::imp::write::hd9cb4c1797101742
   2:     0x560fde7102ff - std::panicking::default_hook::{{closure}}::h154dea97b11a961f
   3:     0x560fde70ffd5 - std::panicking::default_hook::h7b2373844128ce08
   4:     0x560fde710797 - std::panicking::rust_panic_with_hook::h8d52d23c1df454da
   5:     0x560fde7105d4 - std::panicking::begin_panic::h031e0a076e248818
   6:     0x560fde710549 - std::panicking::begin_panic_fmt::hcd972326ec953c01
   7:     0x560fde7104d7 - rust_begin_unwind
   8:     0x560fde75485d - core::panicking::panic_fmt::h519452995771b90d
   9:     0x560fde755579 - core::slice::slice_index_len_fail::h8b5abc07001c836b
  10:     0x560fde42f842 - libpijul::optimal_diff::<impl libpijul::backend::T<A, R>>::diff::h814aa2df53821676
  11:     0x560fde458b1c - libpijul::record::<impl libpijul::backend::T<A, R>>::diff_with_binary::h18f2bc560297272f
  12:     0x560fde457e1c - libpijul::record::<impl libpijul::backend::T<A, R>>::record_all::h330d935d90ddf0fd
  13:     0x560fde45871e - libpijul::record::<impl libpijul::backend::T<A, R>>::record_all::h330d935d90ddf0fd
  14:     0x560fde456dae - libpijul::record::<impl libpijul::backend::T<sanakirja::transaction::MutTxn<'env, ()>, T>>::record::he7e3efd8287bc20f
  15:     0x560fde524e8d - pijul::commands::record::run::he1606db60931ee01
  16:     0x560fde53e768 - pijul::main::hb86d33788bf4db00
  17:     0x560fde718e37 - __rust_maybe_catch_panic
  18:     0x560fde71326d - std::rt::lang_start::h654cbbacaf320c39
  19:     0x7fd0e3f2b52f - __libc_start_main
  20:     0x560fde333079 - _start
                        at ../sysdeps/x86_64/start.S:120
  21:                0x0 - <unknown>
pmeunier commented on March 24, 2017

Hi! Could you run it with RUST_LOG=debug?

ocharles commented on March 25, 2017

Sure, the log has been uploaded to https://ocharles.org.uk/pijul.log (it's 15Mb!)

pmeunier commented on March 27, 2017

This could be fixed by patch #AdFfiKQmOiO3GMCKuJYDtGrjrEqTNIeYptnTDCxm3Frh93E5F-2vgIpj5lrf7SbillDH8rI9wuOwWG-xyxyjM4c

Can you try? If not, I'll make a new release and update NixOS.

ocharles commented on March 29, 2017

I seem to be able to record again, thanks!