You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Managed to reproduce it with a nodejs app that tries to open a file that doesn't exist neither in my local machine, nor in the remote target pod. The crash doesn't happen on debug logs.
thread '<unnamed>' panicked at /home/meowjesty/.rustup/toolchains/nightly-2024-10-11-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:260:26:
cannot access a Thread Local Storage value during or after destruction: AccessError
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at core/src/panicking.rs:221:5:
panic in a functionthat cannot unwind
stack backtrace:
0: 0x7f6109087a0a - std::backtrace_rs::backtrace::libunwind::trace::h1f2bdbcddcdf7b49
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5
1: 0x7f6109087a0a - std::backtrace_rs::backtrace::trace_unsynchronized::h3f655e61c08a7c9d
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
2: 0x7f6109087a0a - std::sys::backtrace::_print_fmt::hf765b11a3e4e09be
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/sys/backtrace.rs:66:9
3: 0x7f6109087a0a - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h87acf85b5211808c
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/sys/backtrace.rs:39:26
4: 0x7f61090afd93 - core::fmt::rt::Argument::fmt::hcc0469ac70529a47
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/core/src/fmt/rt.rs:177:76
5: 0x7f61090afd93 - core::fmt::write::h1830300cff8013e6
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/core/src/fmt/mod.rs:1186:21
6: 0x7f6109083ff3 - std::io::Write::write_fmt::hff4c51c59db7db45
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/io/mod.rs:1839:15
7: 0x7f6109087852 - std::sys::backtrace::BacktraceLock::print::h5e8429acc66fa0b4
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/sys/backtrace.rs:42:9
8: 0x7f61090887fc - std::panicking::default_hook::{{closure}}::h47c5621b8a2933e4
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/panicking.rs:268:22
9: 0x7f6109088642 - std::panicking::default_hook::h4c51255dc678cdff
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/panicking.rs:295:9
10: 0x7f6109088e37 - std::panicking::rust_panic_with_hook::hfa48cfa9339c55df
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/panicking.rs:801:13
11: 0x7f6109088c96 - std::panicking::begin_panic_handler::{{closure}}::hf82473ea8efddcc4
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/panicking.rs:667:13
12: 0x7f6109087ee9 - std::sys::backtrace::__rust_end_short_backtrace::ha3aa6b6ac85645ad
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/sys/backtrace.rs:170:18
13: 0x7f610908895c - rust_begin_unwind
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/std/src/panicking.rs:665:5
14: 0x7f61090ad70d - core::panicking::panic_nounwind_fmt::runtime::h7df6b5d94f5a31c1
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/core/src/panicking.rs:112:18
15: 0x7f61090ad70d - core::panicking::panic_nounwind_fmt::h96fc3e22c4306096
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/core/src/panicking.rs:122:5
16: 0x7f61090ad7a2 - core::panicking::panic_nounwind::h79efc6f334f6baed
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/core/src/panicking.rs:221:5
17: 0x7f61090ad966 - core::panicking::panic_cannot_unwind::hff8fa5fb0642a893
at /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/core/src/panicking.rs:310:5
18: 0x7f610840020f - mirrord_layer::socket::hooks::fcntl_detour::h8c19cd82d94cf29a
at /home/meowjesty/dev/metalbear/mirrord/mirrord/layer/src/socket/hooks.rs:194:1
19: 0x7f6107871d24 - <unknown>
thread caused non-unwinding panic. aborting.
(where mirrord-dev is the locally-built mirrord binary)
crash output
thread '<unnamed>' panicked at /Users/tal/.rustup/toolchains/nightly-2024-10-11-aarch64-apple-darwin/lib/rustlib/src/rust/library/std/src/thread/local.rs:260:26:
cannot access a Thread Local Storage value during or after destruction: AccessError
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at core/src/panicking.rs:221:5:
panic in a function that cannot unwind
stack backtrace:
[1] 60557 illegal hardware instruction RUST_LOG=mirrord=trace exec node
thread '<unnamed>' panicked at /Users/tal/.rustup/toolchains/nightly-2024-10-11-aarch64-apple-darwin/lib/rustlib/src/rust/library/std/src/thread/local.rs:260:26:
cannot access a Thread Local Storage value during or after destruction: AccessError
stack backtrace:
[1] 86419 illegal hardware instruction RUST_BACKTRACE=full RUST_LOG=mirrord=trace exec node
Does not happen with released binaries: the does not happen for example with the released 3.130.0 binary, but when I checked out that tag and built a debug build, the crash did happen with that binary.
Since it only happens with trace level logs and only in debug builds, I would say it's probably related to mirrord_layer_macro::instrument.
Bug Description
Managed to reproduce it with a nodejs app that tries to open a file that doesn't exist neither in my local machine, nor in the remote target pod. The crash doesn't happen on
debug
logs.app.mjs
I'm running it with:
MIRRORD_PROGRESS_MODE=off RUST_LOG=mirrord=trace,warn mirrord exec --config-file mirrord.json node app.mjs
Steps to Reproduce
Backtrace
mirrord layer logs
mirrord intproxy logs
mirrord agent logs
No response
mirrord config
mirrord CLI version
No response
mirrord-agent version
No response
mirrord-operator version (if relevant)
No response
plugin kind and version (if relevant)
No response
Your operating system and version
linux
Local process
app.mjs
Local process version
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: