Skip to content
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

Panic with "Failed to parse patch version" #574

Closed
hasali19 opened this issue Sep 12, 2021 · 3 comments · Fixed by #575
Closed

Panic with "Failed to parse patch version" #574

hasali19 opened this issue Sep 12, 2021 · 3 comments · Fixed by #575
Labels
bug Something isn't working the way that is expected.

Comments

@hasali19
Copy link

Running btm panics with:

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Other("Failed to parse patch version")', /cargo/registry/src/github.com-1ecc6299db9ec823/procfs-0.9.1/src/lib.rs:303:34
   0: bottom::panic_hook
   1: std::panicking::rust_panic_with_hook
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/panicking.rs:595:17
   2: std::panicking::begin_panic_handler::{{closure}}
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/panicking.rs:497:13
   3: std::sys_common::backtrace::__rust_end_short_backtrace
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/sys_common/backtrace.rs:141:18
   4: rust_begin_unwind
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/panicking.rs:493:5
   5: core::panicking::panic_fmt
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/core/src/panicking.rs:92:14
   6: core::result::unwrap_failed
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/core/src/result.rs:1355:5
   7: std::sync::once::Once::call_once::{{closure}}
   8: std::sync::once::Once::call_inner
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/sync/once.rs:418:21
   9: procfs::process::stat::Stat::from_reader
  10: <core::iter::adapters::filter_map::FilterMap<I,F> as core::iter::traits::iterator::Iterator>::next
  11: futures_executor::local_pool::run_executor::{{closure}}
  12: futures_executor::local_pool::block_on
  13: std::sys_common::backtrace::__rust_begin_short_backtrace
  14: core::ops::function::FnOnce::call_once{{vtable.shim}}
  15: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/alloc/src/boxed.rs:1546:9
      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/alloc/src/boxed.rs:1546:9
      std::sys::unix::thread::Thread::new::thread_start
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/sys/unix/thread.rs:71:17
  16: start_thread
  17: <unknown>

I did a bit of investigating and it seems that this is caused by procfs panicking if the kernel patch version is > 255 (4.9.277-117 on my system). I believe this should be fixed on the latest version by eminence/procfs#137, so updating that should hopefully fix this.

@hasali19 hasali19 added the bug Something isn't working the way that is expected. label Sep 12, 2021
@ClementTsang
Copy link
Owner

Thanks for finding and looking into this! I'll look into deploying a patch shortly.

@ClementTsang
Copy link
Owner

Change pushed to master branch, will do a release in a bit.

@ClementTsang
Copy link
Owner

Released in 0.6.4. Thanks for catching this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working the way that is expected.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants