<div dir="ltr">OK, I understand, though I may need some help from someone with interpreting Section headers for Elf. I'll let this group know if I have questions.<div><br></div><div>Thanks again,</div><div> Steve</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 27, 2014 at 4:17 PM, Greg Clayton <span dir="ltr"><<a href="mailto:gclayton@apple.com" target="_blank">gclayton@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On Jan 27, 2014, at 4:02 PM, Steve Pucci <<a href="mailto:spucci@google.com">spucci@google.com</a>> wrote:<br>
<br>
> Thanks, Greg.<br>
><br>
> I think it all makes sense, except for one bit:<br>
><br>
> In ObjectFileELF::SetLoadAddress(), are you proposing I simply call Module::SetLoadAddress as it exists today? That method walks through all sections and checks only section_sp->IsThreadSpecific() to decide whether to load the section, and there's no place to insert an ELF-specific check of the section to see if it's loadable. Is that what you meant, or are you suggesting something else?<br>
<br>
</div>Something else. When the ObjectFileELF parser parses the section headers, it places the flags (or it should if it isn't) into the flags field of the lldb_private::Section. So it should be able to use the flags from its sections to correctly in each lldb_private::Section, and correctly interpret them to know which sections need to be loaded and which don't. So let the ELF plugin that created the sections correctly interpret the flags it put into the sections.<br>
<br>
We then will need to change the Module::SetLoadAddress() to call this new ObjectFile function.<br>
<div class="im"><br>
><br>
> Instead of that I could have ObjectFileELF::SetLoadAddress iterate through the sections as UpdateLoadedSectionsCommon does below, OR I could somehow provide a callback to be called from Module::SetLoadAddress (perhaps by passing in the ObjectFile*).<br>
<br>
</div>It should all be done in the ObjectFileELF::SetLoadAddress function.<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> Thanks,<br>
> Steve<br>
><br>
><br>
><br>
> On Mon, Jan 27, 2014 at 3:14 PM, Greg Clayton <<a href="mailto:gclayton@apple.com">gclayton@apple.com</a>> wrote:<br>
><br>
> On Jan 27, 2014, at 3:05 PM, Greg Clayton <<a href="mailto:gclayton@apple.com">gclayton@apple.com</a>> wrote:<br>
><br>
> > Looks ok except for:<br>
> ><br>
> > This is ELF specific with the file address of zero, and it probably should more be done via flags and asking the section if it is loadable:<br>
> ><br>
> > +void<br>
> > +DynamicLoader::UpdateLoadedSectionsCommon(ModuleSP module, addr_t link_map_addr, addr_t base_addr)<br>
> > +{<br>
> > + Target &target = m_process->GetTarget();<br>
> > + const SectionList *sections = GetSectionListFromModule(module);<br>
> > +<br>
> > + assert(sections && "SectionList missing from loaded module.");<br>
> > +<br>
> > + const size_t num_sections = sections->GetSize();<br>
> > +<br>
> > + for (unsigned i = 0; i < num_sections; ++i)<br>
> > + {<br>
> > + SectionSP section_sp (sections->GetSectionAtIndex(i));<br>
> > + lldb::addr_t new_load_addr = section_sp->GetFileAddress() + base_addr;<br>
> > +<br>
> > + // If the file address of the section is zero then this is not an<br>
> > + // allocatable/loadable section (property of ELF sh_addr). Skip it.<br>
> > + if (new_load_addr == base_addr)<br>
> > + continue;<br>
> > +<br>
> > + target.SetSectionLoadAddress(section_sp, new_load_addr);<br>
> > + }<br>
> > +}<br>
> ><br>
> ><br>
> > There is also a module function that does something similar to this, without the looking for the zero address:<br>
> ><br>
> > bool<br>
> > Module::SetLoadAddress (Target &target, lldb::addr_t offset, bool &changed);<br>
> ><br>
> > So I would propose the following:<br>
> ><br>
> > Update DynamicLoader::UpdateLoadedSectionsCommon() to call into a new function that is a virtual function in ObjectFile:<br>
> ><br>
> > virtual bool SetLoadAddress (addr_t base_addr)<br>
> > {<br>
> > return false;<br>
> > }<br>
> ><br>
> > Then each object file (ObjectFileELF in your case) can choose to do the loading correctly given a single "base_addr":<br>
> ><br>
> > bool<br>
> > ObjectFileELF::SetLoadAddress (addr_t base_addr)<br>
> > {<br>
> > }<br>
> ><br>
> > Then in ObjectFileELF::SetLoadAddress() you can use the section flags that were saved in the lldb_private::Section to properly determine which sections are loadable and which aren't. This function is for a rigid slide of all loadable sections.<br>
> ><br>
> > Does that make sense?<br>
><br>
> I forgot the SetLoadAddress needs a target, and each object file already knows its module, so that doesn't need to be passed, it can be retrieved via the getter function:<br>
><br>
> virtual bool SetLoadAddress (Target &target, addr_t base_addr)<br>
> {<br>
> return false;<br>
> }<br>
><br>
> Then each object file (ObjectFileELF in your case) can choose to do the loading correctly given a single "base_addr":<br>
><br>
> bool<br>
> ObjectFileELF::SetLoadAddress (Target &target, addr_t base_addr)<br>
> {<br>
> ModuleSP module_sp = GetModule();<br>
> if (module_sp)<br>
> {<br>
> ....<br>
> }<br>
> }<br>
><br>
><br>
><br>
> > Greg<br>
> ><br>
> ><br>
> ><br>
> > On Jan 27, 2014, at 2:32 PM, Steve Pucci <<a href="mailto:spucci@google.com">spucci@google.com</a>> wrote:<br>
> ><br>
> >> Hi,<br>
> >><br>
> >> I'd like to have access to a number of methods in DynamicLoaderPOSIXDYLD from the new class I'm working on, DynamicLoaderGDBServer. These methods have no dependency on DynamicLoaderPOSIXDYLD, with two exceptions noted below, so I'm proposing to move them into the base class DynamicLoader.<br>
> >><br>
> >> The two exceptions are the methods UpdateLoadedSections and UnloadSections; in each case there is one line of code that is special to the derived class, and the rest of the code in the method is generic to the base class. In each case I created a XXXCommon() method on the base class with the common code, and created a virtual method XXX() on the base class, which in DynamicLoaderPOSIXDYLD will call the common code and then execute its one line of specialized code.<br>
> >><br>
> >> This patch is intended to have no functional difference whatsoever. All 276 tests that are enabled for Ubuntu pass successfully.<br>
> >><br>
> >> Thanks,<br>
> >> Steve<br>
> >><br>
> >><br>
> >> <patch-FactorDynamicLibrary.txt>_______________________________________________<br>
> >> lldb-dev mailing list<br>
> >> <a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a><br>
> >> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev</a><br>
> ><br>
> > _______________________________________________<br>
> > lldb-dev mailing list<br>
> > <a href="mailto:lldb-dev@cs.uiuc.edu">lldb-dev@cs.uiuc.edu</a><br>
> > <a href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev</a><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>