So node_exporter was crashing on my PC and now I'm bisecting kernel configs to figure out what triggers what smells like a Go runtime bug that everyone assumed was a hardware issue but now I can reproduce it on three Intel hosts and one AMD. I'm not sleeping tonight, am I.
-
Show this thread
-
Now it appears the *toolchain* used to compile the kernel matters. Same GCC/ld version, two different hosts, both kernels cause the issue. Different GCC/ld version, third host, kernel is fine. Moving kernels across hosts it's the kernels that matter, not the hosts I run them on.
2 replies 1 retweet 7 likesShow this thread -
Replying to @marcan42
Oh good grief, so you're looking at a compiler bug introducing a kernel bug introducing a userspace bug? That's gonna be hell to debug x.x
1 reply 0 retweets 1 like
Perhaps a compiler bug introducing a kernel bug introducing a runtime bug introducing an application bug. Yeah, fun times ahead. Could also just be a runtime bug that is triggered by a very specific set of circumstances, though, where memory layout matters in weird ways.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.