Getting a "Index out of range error while upgrading emsdk version to 3.1.18 ,3.1.19 and even in 3.1.10" previously my test app was building fine with emsdk 1.39.20

[Pryagrawal]

Please include the following in your bug report:

Version of emscripten/emsdk: 3.1.18 ,3.1.10 ,3.1.20

em++: warning: EXTRA_EXPORTED_RUNTIME_METHODS is deprecated, please use EXPORTED_RUNTIME_METHODS instead [-Wdeprecated]
Traceback (most recent call last):
  File "/Users/agrawalpriya/emsdk/upstream/emscripten/em++.py", line 14, in <module>
    sys.exit(emcc.run(sys.argv))
  File "/Users/agrawalpriya/emsdk/upstream/emscripten/emcc.py", line 1168, in run
    phase_calculate_system_libraries(state, linker_arguments, linker_inputs, newargs)
  File "/Users/agrawalpriya/emsdk/python/3.9.2_64bit/lib/python3.9/contextlib.py", line 79, in inner
    return func(*args, **kwds)
  File "/Users/agrawalpriya/emsdk/upstream/emscripten/emcc.py", line 2726, in phase_calculate_system_libraries
    extra_files_to_link += system_libs.calculate(all_linker_inputs, newargs, forced=state.forced_stdlibs)
  File "/Users/agrawalpriya/emsdk/upstream/emscripten/tools/system_libs.py", line 1885, in calculate
    handle_reverse_deps(input_files)
  File "/Users/agrawalpriya/emsdk/upstream/emscripten/tools/system_libs.py", line 1729, in handle_reverse_deps
    symbolses = building.llvm_nm_multiple([os.path.abspath(t) for t in input_files])
  File "/Users/agrawalpriya/emsdk/python/3.9.2_64bit/lib/python3.9/contextlib.py", line 79, in inner
    return func(*args, **kwds)
  File "/Users/agrawalpriya/emsdk/upstream/emscripten/tools/building.py", line 184, in llvm_nm_multiple
    for key, value in parse_llvm_nm_symbols(results.stdout).items():
  File "/Users/agrawalpriya/emsdk/upstream/emscripten/tools/building.py", line 574, in parse_llvm_nm_symbols
    status = line[entry_pos + 11] # Skip address, which is always fixed-length 8 chars.
IndexError: string index out of range
make[2]: *** [TestProfileWebTestApp.js] Error 1
make[1]: *** [CMakeFiles/TestProfileWebTestApp.dir/all] Error 2
make: *** [all] Error 2
emmake: error: 'make -j4' failed (returned 2)
Please make sure that cmake is installed.

[sbc100]

Can you should the completely failing command? With cmake you can use this by running make VERBOSE=1 (also using the ninja build tool will do this automatically when a command fails so you might want to consider switching to that using -G Ninja when running cmake).

[Pryagrawal]

Can you should the completely failing command? With cmake you can use this by running make VERBOSE=1 (also using the ninja build tool will do this automatically when a command fails so you might want to consider switching to that using -G Ninja when running cmake).

I have try to add verbose by using "set (CMAKE_VERBOSE_MAKEFILE ON) " on cmakelist.txt file ,but not get enough message [100%] Linking CXX executable TestProfileWebTestApp.js
/usr/local/Cellar/cmake/3.22.2/bin/cmake -E cmake_link_script CMakeFiles/TestProfileWebTestApp.dir/link.txt --verbose=1
/Users/agrawalpriya/emsdk/upstream/emscripten/em++ -g -O0 -D_DEBUG=1 -s EXTRA_EXPORTED_RUNTIME_METHODS=['ccall','getValue','setValue','UTF8ToString'] -s EXPORTED_FUNCTIONS=['_main_web'] -lidbfs.js -s FETCH=1 -s FORCE_FILESYSTEM=1 -s DEMANGLE_SUPPORT=1 -s DISABLE_EXCEPTION_CATCHING=0 -s WASM=1 -s ERROR_ON_UNDEFINED_SYMBOLS=0 --std=c++11 -s ALLOW_MEMORY_GROWTH=1 @CMakeFiles/TestProfileWebTestApp.dir/objects1.rsp -o TestProfileWebTestApp.js @CMakeFiles/TestProfileWebTestApp.dir/linklibs.rsp
em++: warning: EXTRA_EXPORTED_RUNTIME_METHODS is deprecated, please use EXPORTED_RUNTIME_METHODS instead [-Wdeprecated]
Traceback (most recent call last):
File "/Users/agrawalpriya/emsdk/upstream/emscripten/em++.py", line 14, in
sys.exit(emcc.run(sys.argv))
File "/Users/agrawalpriya/emsdk/upstream/emscripten/emcc.py", line 1202, in run
phase_calculate_system_libraries(state, linker_arguments, linker_inputs, newargs)
File "/Users/agrawalpriya/emsdk/python/3.9.2_64bit/lib/python3.9/contextlib.py", line 79, in inner
return func(*args, **kwds)
File "/Users/agrawalpriya/emsdk/upstream/emscripten/emcc.py", line 2845, in phase_calculate_system_libraries
extra_files_to_link += system_libs.calculate(all_linker_inputs, newargs, forced=state.forced_stdlibs)
File "/Users/agrawalpriya/emsdk/upstream/emscripten/tools/system_libs.py", line 1954, in calculate
handle_reverse_deps(input_files)
File "/Users/agrawalpriya/emsdk/upstream/emscripten/tools/system_libs.py", line 1791, in handle_reverse_deps
symbolses = building.llvm_nm_multiple([os.path.abspath(t) for t in input_files])
File "/Users/agrawalpriya/emsdk/python/3.9.2_64bit/lib/python3.9/contextlib.py", line 79, in inner
return func(*args, **kwds)
File "/Users/agrawalpriya/emsdk/upstream/emscripten/tools/building.py", line 185, in llvm_nm_multiple
for key, value in parse_llvm_nm_symbols(results.stdout).items():
File "/Users/agrawalpriya/emsdk/upstream/emscripten/tools/building.py", line 578, in parse_llvm_nm_symbols
status = line[entry_pos + 11] # Skip address, which is always fixed-length 8 chars.
IndexError: string index out of range
make[2]: *** [TestProfileWebTestApp.js] Error 1
make[1]: *** [CMakeFiles/TestProfileWebTestApp.dir/all] Error 2
make: *** [all] Error 2
emmake: error: 'make -j4' failed (returned 2)
Please make sure that cmake is installed.

[sbc100]

Could you modify tools/building.py and print results.stdout? that should be enough for us to be able to figure out what is going on the parse failure.

[Pryagrawal]

results.stdout

hi
@sbc100 can you suggest which line i should modify in tools/building.py to see the parse error

[sbc100]

Can you add print(results.stdout) between lines 184 and 185

[Pryagrawal]

error_print.docx
i have added the print statement here ,please check the logs

[sbc100]

Could you attach as a simple text file? The docx seems to be causing google docs to struggle.

[Pryagrawal]

Could you attach as a simple text file? The docx seems to be causing google docs to struggle.

error.txt.

[sbc100]

It looks like some extra chars might have ended up in that text file somehow. Can you run your build command with the > error.txt appended to the end? That should write the contents directly to the error.txt file.

[Pryagrawal]

It looks like some extra chars might have ended up in that text file somehow. Can you run your build command with the > error.txt appended to the end? That should write the contents directly to the error.txt file.

sure
error.txt

[sbc100]

I figured out the problem. It looks line some of your object files were built with an older version of clang for example:
/Users/agrawalpriya/TestACE/imports/potluck/libraries/web/release/libPotluckStd.a:MTTestSuite.cpp.o

This object file contains symbols which looks like they must have come from an older version of llvm/clang. Can you try rebuilding all of these ?