[Lldb-commits] [PATCH] Add qModuleInfo request in order to get module information (uuid, triple, ..) by module path from remote platform.

[Greg Clayton]

> On Feb 20, 2015, at 2:56 PM, Oleksiy Vyalov <ovyalov at google.com> wrote:
> 
> Hi Vince,
> 
> In http://reviews.llvm.org/D7709#127748, @vharron wrote:
> 
>> Hi all,
>> 
>> In this instance, we are using this uuid to determine if the module is already cached on the host, right?
> 
> 
> yes, the plan to have local cache on host side with UUID used a key.
> 
>> If a fat binary has multiple architectures in a single file and each arch has it's own uuid, wouldn't we just combine (add/xor/whatever) the uuids to get a single uuid for the entire file?
> 
> 
> My understanding that in case of a fat binary with multiple architectures there is still a single UUID that represents a whole module's binary file, i.e. UUID shouldn't be tied to an architecture.

That is not correct for MacOSX. Each slice has its own UUID value. The qModuleInfo might be able to return the file offset and file set as well so we can download and cache only the slice we need?

> 
> http://reviews.llvm.org/D7709
> 
> EMAIL PREFERENCES
>  http://reviews.llvm.org/settings/panel/emailpreferences/
> 
>