https://bugs.llvm.org/show_bug.cgi?id=37074
Bug ID: 37074
Summary: Can't build libLLVMSupport.a on ARM CPU
Product: lldb
Version: 6.0
Hardware: PC
OS: Linux
Status: NEW
Severity: release blocker
I'm looking at how the LLDB minidump reader creates the list of modules:
void ProcessMinidump::ReadModuleList() {
...
const auto file_spec = FileSpec(name.getValue(), true);
ModuleSpec module_spec = file_spec;
Status error;
lldb::ModuleSP module_sp = GetTarget().GetSharedModule(module_spec, &err
> On Apr 10, 2018, at 11:32 AM, Leonard Mosescu via lldb-dev
> wrote:
>
> I'm looking at how the LLDB minidump reader creates the list of modules:
>
> void ProcessMinidump::ReadModuleList() {
> ...
> const auto file_spec = FileSpec(name.getValue(), true);
> ModuleSpec module_spec = fi
Thanks Greg! It makes sense and looking at the code it's already
implemented along those lines: Target::GetSharedModule() defaults to
Platform::GetSharedModule() if the initial attempt to get the module fails.
The part I'd like to understand is if there's a precedence for modules
which don't have
> On Apr 10, 2018, at 2:30 PM, Leonard Mosescu wrote:
>
> Thanks Greg! It makes sense and looking at the code it's already implemented
> along those lines: Target::GetSharedModule() defaults to
> Platform::GetSharedModule() if the initial attempt to get the module fails.
>
> The part I'd lik
>
>
> No. Each binary knows how to tell LLDB what target triple it is. PECOFF
> files will always map to the host windows platform or remote-windows when
> not on a Windows host computer. If you say "file a.out" and give it a
> PECOFF file, just do "target list" and see the platform was selected fo
> On Apr 10, 2018, at 3:21 PM, Leonard Mosescu wrote:
>
>
> No. Each binary knows how to tell LLDB what target triple it is. PECOFF files
> will always map to the host windows platform or remote-windows when not on a
> Windows host computer. If you say "file a.out" and give it a PECOFF file,
On Tue, Apr 10, 2018 at 3:12 PM, Greg Clayton via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
>
>
> On Apr 10, 2018, at 2:30 PM, Leonard Mosescu wrote:
>
> Thanks Greg! It makes sense and looking at the code it's already
> implemented along those lines: Target::GetSharedModule() defaults to
> Plat
>
> Ahh. So then hopefully it extracts the triple from the mini dump file and
> sets it correctly which gets us right platform set?
>
Yes, this part seems to be working fine.
Just to make sure I understand: we need a file with the debug info (e.g.,
> a PDB), but we shouldn't need the actual exec
