wasm-ld error "unknown symbol kind" UNREACHABLE executed

[Angad Gupta]

Anyone encountered issue with wasm-ld error "UNREACHABLE executed". I am using latest toolchain 2.0.12. Any clues how to debug this to get too symbol causing the issue?

Error Desciption:
unknown symbol kind
UNREACHABLE executed at /opt/s/w/ir/cache/builder/emscripten-releases/llvm-project/lld/wasm/InputFiles.cpp:538!
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace.
Stack dump:
0. Program arguments: /Users/anggupta/unisight_emscripten_new/upstream/bin/wasm-ld @/var/folders/yd/_8lm5d817ngbnscpytnq2cfh0000gn/T/emscripten_zeo4if9g.rspStack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):0 libLLVM.dylib      0x00000001091035fb llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 43
1 libLLVM.dylib      0x0000000109102368 llvm::sys::RunSignalHandlers() + 248
2 libLLVM.dylib      0x0000000109103c60 SignalHandler(int) + 288
3 libsystem_platform.dylib 0x00007fff67fbd5fd _sigtramp + 29
4 libsystem_platform.dylib 0x000000010d4e4b8d _sigtramp + 18446603343289808301
5 libsystem_c.dylib    0x00007fff67e93808 abort + 120
6 libLLVM.dylib      0x000000010903c063 llvm::llvm_unreachable_internal(char const*, char const*, unsigned int) + 467

[Angad Gupta]

Error screenshot attached.

[Thomas Lively]

Yes, there was an issue on tip of tree LLVM for a little bit in which the object file ABI was broken such that it emitted new symbol and relocation types that older lld versions did not understand, leading in some cases to the crash you’re seeing. Upgrading to 2.0.13 will fix the problem because its lld understands the new symbols. Meanwhile the ABI breakage has been reverted in upstream LLVM.

--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/571a643f-b022-4c5c-a9db-e3efcea4c1e1n%40googlegroups.com.

[Sam Clegg]

On Wed, Jan 27, 2021 at 10:48 AM 'Thomas Lively' via emscripten-discuss <emscripte...@googlegroups.com> wrote:

Yes, there was an issue on tip of tree LLVM for a little bit in which the object file ABI was broken such that it emitted new symbol and relocation types that older lld versions did not understand, leading in some cases to the crash you’re seeing. Upgrading to 2.0.13 will fix the problem because its lld understands the new symbols. Meanwhile the ABI breakage has been reverted in upstream LLVM.

Shouldn't this have only affected folks with an LLVM version mismatch?  (i.e. folks with object files built with a newer version of llvm than the emscripten one?)   User who use only emscripten 2.0.12 should not affected by this crash should they? 

On Wed, Jan 27, 2021 at 07:06 Angad Gupta <gupta...@gmail.com> wrote:

Error screenshot attached.

On Wednesday, 27 January 2021 at 20:34:42 UTC+5:30 Angad Gupta wrote:

Anyone encountered issue with wasm-ld error "UNREACHABLE executed". I am using latest toolchain 2.0.12. Any clues how to debug this to get too symbol causing the issue?

Error Desciption:
unknown symbol kind
UNREACHABLE executed at /opt/s/w/ir/cache/builder/emscripten-releases/llvm-project/lld/wasm/InputFiles.cpp:538!
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace.
Stack dump:
0. Program arguments: /Users/anggupta/unisight_emscripten_new/upstream/bin/wasm-ld @/var/folders/yd/_8lm5d817ngbnscpytnq2cfh0000gn/T/emscripten_zeo4if9g.rspStack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):0 libLLVM.dylib      0x00000001091035fb llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 43
1 libLLVM.dylib      0x0000000109102368 llvm::sys::RunSignalHandlers() + 248
2 libLLVM.dylib      0x0000000109103c60 SignalHandler(int) + 288
3 libsystem_platform.dylib 0x00007fff67fbd5fd _sigtramp + 29
4 libsystem_platform.dylib 0x000000010d4e4b8d _sigtramp + 18446603343289808301
5 libsystem_c.dylib    0x00007fff67e93808 abort + 120
6 libLLVM.dylib      0x000000010903c063 llvm::llvm_unreachable_internal(char const*, char const*, unsigned int) + 467

--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/571a643f-b022-4c5c-a9db-e3efcea4c1e1n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAJZD_EWVmJz3YbgFoNjnMaVCHuQCfwmxTo3JDc7bBjcYsm4OAQ%40mail.gmail.com.