chettoy / apexsky

https://apex.chettoy.com
GNU General Public License v3.0
146 stars 81 forks source link

some of the offsets in the Miscellaneous section are missing :CWeaponX!m_flProjectileSpeed #145

Closed softwarejob closed 3 months ago

softwarejob commented 3 months ago

IMG_3729

chettoy commented 3 months ago

Don't worry, CWeaponX!m_flProjectileSpeed is no longer read from the Miscellaneous section. note, however, that SpectatorList will be read from the Miscellaneous section.

softwarejob commented 3 months ago

c@c-System-Product-Name:~$ sudo ./apexsky_dma kvm --config /home/c/offsets.ini 2024-08-22T16:36:13.221655Z INFO apexsky_dmalib::mem::memprocfs_impl: leechcore device: fpga at apexsky_dmalib/src/mem/memprocfs_impl.rs:43 in apexsky_dmalib::access::create_os_instance with connector: PCILeech("fpga") in apexsky_dmalib::access::io_thread

2024-08-22T16:36:13.221658Z WARN apexsky::offsets: Reading offsets from /home/c/offsets.ini at apexsky/src/offsets/mod.rs:13

2024-08-22T16:36:13.221731Z ERROR apexsky_dma: connector: PCILeech("fpga"), e: No such file or directory (os error 2), e: No such file or directory (os error 2) at apexsky_dma/src/main.rs:190

Press enter to exit.. 2024-08-22T16:36:13.221737Z WARN apexsky_dma::usermod_thr: e: No such file or directory (os error 2) at apexsky_dma/src/usermod_thr.rs:71

thread '' panicked at src/apex_offsets/offsets.rs:342:1: Failed to parse offsets data.: Failed to read value CWeaponX!m_flProjectileSpeed in section Miscellaneous in offsets file. note: run with RUST_BACKTRACE=1 environment variable to display a backtrace thread 'tokio-runtime-worker' panicked at /home/runner/work/apexsky/apexsky/apex_dma/lib/skyapex/skyapex-sdk/src/module/offsets_loader.rs:44:1: called Result::unwrap() on an Err value: error while executing at wasm backtrace: 0: 0x5f490 - skyapex-585d4e796d33096b.wasm!rust_start_panic 1: 0x5f164 - skyapex-585d4e796d33096b.wasm!rust_panic 2: 0x5f0c0 - skyapex-585d4e796d33096b.wasm!std::panicking::rust_panic_with_hook::h9008010525035331 3: 0x5e4e8 - skyapex-585d4e796d33096b.wasm!std::panicking::begin_panic_handler::{{closure}}::hfe0359372b2a9e3c 4: 0x5e465 - skyapex-585d4e796d33096b.wasm!std::sys::backtrace::rust_end_short_backtrace::h1c3135666f31eba2 5: 0x5eac1 - skyapex-585d4e796d33096b.wasm!rust_begin_unwind 6: 0x6d425 - skyapex-585d4e796d33096b.wasm!core::panicking::panic_fmt::h662bd2e510224686 7: 0x6ef2a - skyapex-585d4e796d33096b.wasm!core::result::unwrap_failed::hff4419b07f7e7b63 8: 0x26a98 - skyapex-585d4e796d33096b.wasm!skyapex::apex_offsets::offsets::export_offsets::h2186ecbecdf1e160 9: 0x3fd27 - skyapex-585d4e796d33096b.wasm!export_offsets_from_file

Caused by: wasm trap: wasm unreachable instruction executed note: run with RUST_BACKTRACE=1 environment variable to display a backtrace thread 'tokio-runtime-worker' panicked at core/src/panicking.rs:221:5: panic in a function that cannot unwind stack backtrace: 0: 0x5780c5af5c4d - ::fmt::h8715143191f8c23b 1: 0x5780c5b2544b - core::fmt::write::hd62d3df0c95f7bba 2: 0x5780c5aef713 - std::io::Write::write_fmt::h482a38f35ba22b1f 3: 0x5780c5af72c2 - std::panicking::default_hook::{{closure}}::h2c9e44cde99fb07e 4: 0x5780c5af6f2e - std::panicking::default_hook::h1b794a004c8d07c1 5: 0x5780c5af7bbf - std::panicking::rust_panic_with_hook::h57cf852c292ccee4 6: 0x5780c5af7873 - std::panicking::begin_panic_handler::{{closure}}::hd3053864430fffca 7: 0x5780c5af6139 - std::sys::backtrace::rust_end_short_backtrace::h5474d59fe5aad636 8: 0x5780c5af7534 - rust_begin_unwind 9: 0x5780c5b22445 - core::panicking::panic_nounwind_fmt::h7dacece5f7eeb410 10: 0x5780c5b224d2 - core::panicking::panic_nounwind::hf32bbd7e091dbdce 11: 0x5780c5b22616 - core::panicking::panic_cannot_unwind::h1a518cdedb6f76b6 12: 0x5780c50479d7 - import_offsets 13: 0x5780c5044b8a - core::ops::function::FnOnce::call_once::h5b3821c72b3f4ada 14: 0x5780c2cdbe89 - once_cell::imp::OnceCell::initialize::{{closure}}::hbcaca885abd1b683 15: 0x5780c5ac6ddc - once_cell::imp::initialize_or_wait::hf0dcc04d2798d689 16: 0x5780c2cdbc05 - once_cell::imp::OnceCell::initialize::h2c06265fd5bcd58a 17: 0x5780c2cf090d - ::default::hb781f810411d1bd4 18: 0x5780c2c74511 - apexsky_dma::apexdream::Instance::new::h44e1b64a4590799b 19: 0x5780c2b3f798 - apexsky_dma::workers::actions::actions_loop::{{closure}}::{{closure}}::h451987ed96bc55c1 20: 0x5780c2b3f275 - apexsky_dma::workers::actions::actions_loop::{{closure}}::h2ef8fafafa6a8218 21: 0x5780c2b29d3c - tokio::runtime::task::core::Core<T,S>::poll::h45d82814a85ce80a 22: 0x5780c2bf742c - tokio::runtime::task::harness::Harness<T,S>::poll::h15b376a7420e3a8d 23: 0x5780c53df7ce - tokio::runtime::scheduler::multi_thread::worker::Context::run_task::hb190ec826cf64875 24: 0x5780c53de542 - tokio::runtime::scheduler::multi_thread::worker::Context::run::hb7fa0bcb00e36315 25: 0x5780c53d86f6 - tokio::runtime::context::scoped::Scoped::set::h695a22b9d0f5b9c3 26: 0x5780c53cd5ff - tokio::runtime::context::runtime::enter_runtime::hf2b45dd7839b7ee1 27: 0x5780c53de06c - tokio::runtime::scheduler::multi_thread::worker::run::hab30e77e44d5258d 28: 0x5780c53e3693 - tokio::runtime::task::core::Core<T,S>::poll::h5c3273719ad62ad5 29: 0x5780c53c31d1 - tokio::runtime::task::harness::poll_future::h86a2de5972bf1496 30: 0x5780c53c1016 - tokio::runtime::task::harness::Harness<T,S>::poll_inner::h764ef897d12b754d 31: 0x5780c53c0e04 - tokio::runtime::task::harness::Harness<T,S>::poll::h976aff6bdfddeba8 32: 0x5780c53ee872 - tokio::runtime::blocking::pool::Inner::run::h7d49ac8db5cc3003 33: 0x5780c53c364e - std::sys::backtrace::rust_begin_short_backtrace::h99aba7b908b8f6f7 34: 0x5780c53c3e04 - core::ops::function::FnOnce::call_once{{vtable.shim}}::he10f13195f0f9d78 35: 0x5780c5afcedb - std::sys::pal::unix::thread::Thread::new::thread_start::hb496351d817698d4 36: 0x7d957789ca94 - start_thread at ./nptl/pthread_create.c:447:8 37: 0x7d9577929c3c - clone3 at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 38: 0x0 - thread caused non-unwinding panic. aborting. Aborted

softwarejob commented 3 months ago

Where could the issue be? I only replaced the offsets.ini file. When I run sudo ./apexsky_dma kvm --config /home/c/offsets.ini, errors keep showing up.

chettoy commented 3 months ago

Where could the issue be? I only replaced the offsets.ini file. When I run sudo ./apexsky_dma kvm --config /home/c/offsets.ini, errors keep showing up.

Don't worry, CWeaponX!m_flProjectileSpeed is no longer read from the Miscellaneous section. note, however, that SpectatorList will be read from the Miscellaneous section.

The version you're using may be older than that change.