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

thread 'Worker' panicked with invalid offset when show outgoing call #18800

Closed
lh123 opened this issue Dec 31, 2024 · 1 comment · Fixed by #18802
Closed

thread 'Worker' panicked with invalid offset when show outgoing call #18800

lh123 opened this issue Dec 31, 2024 · 1 comment · Fixed by #18802
Assignees
Labels
C-bug Category: bug

Comments

@lh123
Copy link
Contributor

lh123 commented Dec 31, 2024

rust-analyzer version: 0.3.2237-standalone (59bc7b4 2024-12-29)

rustc version: rustc 1.83.0 (90b35a623 2024-11-26)

editor or extension: VSCode

code snippet to reproduce:

fn main() {
    let a  = Some(5).take();
    //               ^^^^  invoke outgoing call on take
}
thread 'Worker' panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\line-index-0.1.2\src/lib.rs:111:35:
invalid offset
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf\library/std\src\panicking.rs:665
   1: core::panicking::panic_fmt
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf\library/core\src\panicking.rs:74
   2: core::panicking::panic_display
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf\library/core\src\panicking.rs:264
   3: core::option::expect_failed
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf\library/core\src\option.rs:2021
   4: rust_analyzer::lsp::to_proto::range
   5: alloc::vec::in_place_collect::<impl alloc::vec::spec_from_iter::SpecFromIter<T,I> for alloc::vec::Vec<T>>::from_iter
   6: rust_analyzer::handlers::request::handle_call_hierarchy_outgoing
   7: core::ops::function::FnOnce::call_once{{vtable.shim}}
@lh123 lh123 added the C-bug Category: bug label Dec 31, 2024
@lh123
Copy link
Contributor Author

lh123 commented Dec 31, 2024

may relative:
#17762
#14839

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants