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
Occasionally, we run into binaries that use CPU op codes that are not available on the machine it's running. Sometime this happens because we download and install pre-compiled binaries, sometimes because we build on a modern CPU architecture but then run on an older one. In the past, we've seen "illegal instruction" core dumps due to for instance a machine to supporting the AVX2 instruction.
Idea
Troubleshooting these problems can be tricky. Sometimes it's due to a dependency, you built years ago. It would be useful if one could at least use scan known binaries and libraries for CPU opcodes and print out a summary. It does not have to be perfect - only good enough to give suggestions.
Tools that can be useful for this:
ldd
objdump -d
...?
The text was updated successfully, but these errors were encountered:
(scribbling down an old idea of mine)
Background
Occasionally, we run into binaries that use CPU op codes that are not available on the machine it's running. Sometime this happens because we download and install pre-compiled binaries, sometimes because we build on a modern CPU architecture but then run on an older one. In the past, we've seen "illegal instruction" core dumps due to for instance a machine to supporting the
AVX2
instruction.Idea
Troubleshooting these problems can be tricky. Sometimes it's due to a dependency, you built years ago. It would be useful if one could at least use scan known binaries and libraries for CPU opcodes and print out a summary. It does not have to be perfect - only good enough to give suggestions.
Tools that can be useful for this:
ldd
objdump -d
The text was updated successfully, but these errors were encountered: