[llvm-bugs] [Bug 41802] New: [wasm-ld] zlib crash

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=41802

            Bug ID: 41802
           Summary: [wasm-ld] zlib crash
           Product: lld
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: All Bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: alonzakai at gmail.com
                CC: llvm-bugs at lists.llvm.org, peter.smith at linaro.org

Created attachment 21911
  --> https://bugs.llvm.org/attachment.cgi?id=21911&action=edit
all files but libc (too big with it all together)

This crashes:

wasm-ld src_0.o libz.a libc.bc libc-wasm.bc libdlmalloc.bc libpthreads_stub.bc
libcompiler_rt.a libcompiler_rt_wasm.a libc_rt_wasm.a -mllvm
-combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm
-disable-lsr --export __wasm_call_ctors --export __data_end --export main
--export malloc --export free --export setThrew --export __errno_location
--export fflush -z stack-size=5242880 --initial-memory=16777216 --no-entry
--max-memory=16777216 --global-base=1024 -o src.c.o.wasm --allow-undefined
--import-memory --import-table --lto-O0

and the crash says it is on

lld::wasm::FunctionSymbol::getFunctionIndex()

Valgrind confirms with "Invalid read of size 1" on that function.

Noticed this when working on
https://github.com/emscripten-core/emscripten/pull/8550 , that is, when getting
emscripten to properly test LTO. The attached files are from running
wasmlto0.test_zlib on that PR (specifically
84d61dac52c8a74898bb953916d0f4654348163e).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190508/b1a4a159/attachment.html>