-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
37 error in hivescan unexpectedeof #38
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #38 +/- ##
=======================================
Coverage 33.01% 33.01%
=======================================
Files 36 36
Lines 1136 1136
=======================================
Hits 375 375
Misses 761 761 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now I get another error message:
thread 'main' panicked at src/bin/hivescan/regtreebuilder.rs:80:9:
assertion failed: !self.subtrees.contains_key(&nk_offset)
stack backtrace:
0: rust_begin_unwind
at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:645:5
1: core::panicking::panic_fmt
at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/panicking.rs:72:14
2: core::panicking::panic
at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/panicking.rs:127:5
3: hivescan::regtreebuilder::RegTreeBuilder::insert_nk
at ./src/bin/hivescan/regtreebuilder.rs:80:9
4: hivescan::regtreebuilder::RegTreeBuilder::from_hive
at ./src/bin/hivescan/regtreebuilder.rs:65:17
5: hivescan::hivescanapplication::HiveScanApplication::run
at ./src/bin/hivescan/hivescanapplication.rs:38:23
6: hivescan::main
at ./src/bin/hivescan/main.rs:38:13
7: core::ops::function::FnOnce::call_once
at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
fix #37