Hi!
When running dump_syms on a Windows host machine to process Android native binaries (.so), the tool outputs corrupted file paths in the generated .sym files.
At this moment the tool dynamically determines path-parsing rules based on the target binary format (forcing Linux path-handling mechanics whenever it decodes a DWARF/ELF section) [ref], it inherently fails to recognize a Windows C:\ absolute path style, and therefore concatenates compilation_dir with file_name (which is abs path) [ref].
As a result, output has recordings like this:
FILE 116 C:/Users/s_petrovskiy/Documents/work/repo/sandbox/apps/sandbox/.cxx/Debug/14223k59/arm64-v8a/C:/Users/s_petrovskiy/Documents/work/repo/sandbox/apps/sandbox/src/main.cpp
Hi!
When running dump_syms on a Windows host machine to process Android native binaries (.so), the tool outputs corrupted file paths in the generated .sym files.
At this moment the tool dynamically determines path-parsing rules based on the target binary format (forcing Linux path-handling mechanics whenever it decodes a DWARF/ELF section) [ref], it inherently fails to recognize a Windows C:\ absolute path style, and therefore concatenates compilation_dir with file_name (which is abs path) [ref].
As a result, output has recordings like this:
FILE 116 C:/Users/s_petrovskiy/Documents/work/repo/sandbox/apps/sandbox/.cxx/Debug/14223k59/arm64-v8a/C:/Users/s_petrovskiy/Documents/work/repo/sandbox/apps/sandbox/src/main.cpp