Re: [lldb-dev] lldb10 can not hit break point on windows platform

2020-10-19 Thread Greg Clayton via lldb-dev
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

Re: [lldb-dev] [RFC] Segmented Address Space Support in LLDB

2020-10-19 Thread Greg Clayton via lldb-dev
> On Oct 19, 2020, at 2:56 PM, Jonas Devlieghere via lldb-dev > wrote: > > We want to support segmented address spaces in LLDB. Currently, all of LLDB’s > external API, command line interface, and internals assume that an address in > memory can be addressed unambiguously as an addr_t (aka u

[lldb-dev] [RFC] Segmented Address Space Support in LLDB

2020-10-19 Thread Jonas Devlieghere via lldb-dev
We want to support segmented address spaces in LLDB. Currently, all of LLDB’s external API, command line interface, and internals assume that an address in memory can be addressed unambiguously as an addr_t (aka uint64_t). To support a segmented address space we’d need to extend addr_t with a discr

Re: [lldb-dev] lldb10 can not hit break point on windows platform

2020-10-19 Thread Adrian McCarthy via lldb-dev
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