search for: debuginfodwarftests

...h .debug_str provided it tries to take ranges from there, tries to get DWO name to open it and fails. Though I did not find why it tries to scan .dwo. I tried to comment these lines (335-339) and no tests were failing for me, at least I tried running tests from \llvm\test\DebugInfo and running DebugInfoDWARFTests. It seems to me these lines are either untested or useless (?). So my question is probably next: what is the case when we need to scan .dwo for extracting ranges, should not address data be accessible from main object always ? I wonder if these lines really do useful job ?? Best regards, Georg...

Dear testers, 5.0.0-rc1 has just been tagged. Please build, test and upload binaries to the sftp. Let me know if there are any issues. I'll upload sources, docs, and your binaries to the pre-release website once they're ready. Thanks, Hans

...ests/ExecutionEngine/CMakeFiles/ExecutionEngineTests.dir 4.0K build/unittests/Demangle/CMakeFiles/DemangleTests.dir 4.0K build/unittests/DebugInfo/PDB/CMakeFiles/DebugInfoPDBTests.dir 4.0K build/unittests/DebugInfo/MSF/CMakeFiles/DebugInfoMSFTests.dir 4.0K build/unittests/DebugInfo/DWARF/CMakeFiles/DebugInfoDWARFTests.dir 4.0K build/unittests/DebugInfo/CodeView/CMakeFiles/DebugInfoCodeViewTests.dir 4.0K build/unittests/DebugInfo/CMakeFiles 4.0K build/unittests/CodeGen/GlobalISel/CMakeFiles/GlobalISelTests.dir 4.0K build/unittests/CodeGen/CMakeFiles/CodeGenTests.dir 4.0K build/unittests/CMakeFiles 4.0K build/unit...