Skip to content
This repository has been archived by the owner on Apr 19, 2022. It is now read-only.

Thread 'Heavy verification' panicked #108

Open
rex4539 opened this issue May 24, 2019 · 2 comments
Open

Thread 'Heavy verification' panicked #108

rex4539 opened this issue May 24, 2019 · 2 comments

Comments

@rex4539
Copy link
Contributor

rex4539 commented May 24, 2019

2019-05-24 13:39:03  INFO sync Processed 3 blocks in 65.38 seconds (0.05 blk/s).	Peers: 10 (act: 0, idl: 10, bad: 0).	Chain: [sch:3040 > req:0 > vfy:1127 > db:533648]
thread 'Heavy verification' panicked at 'internal error: entered unreachable code: Trying to re-verify known block: 0000000000bc082bfee78ba6f8b88215e6a2c1c9ed8afeab1ca6efd1801fa91f', verification/src/chain_verifier.rs:56:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39
   1: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:70
             at src/libstd/sys_common/backtrace.rs:58
   2: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:200
   3: std::panicking::default_hook
             at src/libstd/panicking.rs:215
   4: <std::panicking::begin_panic::PanicPayload<A> as core::panic::BoxMeUp>::get
             at src/libstd/panicking.rs:478
   5: std::panicking::continue_panic_fmt
             at src/libstd/panicking.rs:385
   6: std::panicking::try::do_call
             at src/libstd/panicking.rs:340
Abort trap: 6
@svyatonik
Copy link
Contributor

@rex4539 Are there any chances you're using old version of pzec? We have fixed similar issue ~month ago (in #99).

@rex4539
Copy link
Contributor Author

rex4539 commented May 27, 2019

I’m always compiling from latest master :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants