Thanks, I will take a look.
Greg Clayton 于2020年10月21日周三 上午2:50写道：
> So the good news is the DWARF seems to be valid.
>
> I think LLDB is having problems with this ELF file because it is an object
> file (e_type == ET_REL) or because it has no program headers.
>
> There were some changes made to
So the good news is the DWARF seems to be valid.
I think LLDB is having problems with this ELF file because it is an object file
(e_type == ET_REL) or because it has no program headers.
There were some changes made to LLDB where we would put any section headers
that were contained in program h
Hi, all:
Thanks for your answer. Maybe my description is not clear enough.
MLExecuteTest.exe is just a shell to compile and execute TestFunctin.cpp,
the step is below:
1. call llvm function to compile TestFunction.cpp, this will create
module ,function, block, instruction, and generate binary c
As long as the location TestFunction.cpp:1 has a valid line in the PDB line
tables, this breakpoint should be hit if there is debug info and the internal
PDB parser is parsing things correctly. If you have debug info in your binary,
_and_ if LLDB is able to locate your PDB file, then you should
On Windows, LLVM is migrating to its own debug info reading code (the
Native PDB reader) instead of relying on DIA (a Microsoft-provided
Windows-only DLL for accessing debug info), so that might explain the
difference between the older versions and the current.
I don't know enough about LLDB's mod
Hello,everyone:
I have a problem when download llvm10.0.1 and use lldb to debug my
process on windows10 x64 platform. but with no debug point hit.
the command is
（lldb）target create "D:/code/MLExecuteTest.exe"
Current executable set to 'D:/code/MLExecuteTest.exe' (x86_64)
（lldb）br s -fE:/tes
