[llvm-commits] [llvm] r157505 - /llvm/trunk/lib/Transforms/Instrumentation/GCOVProfiling.cpp

Bill Wendling isanbard at gmail.com
Tue May 29 02:09:03 PDT 2012


On May 28, 2012, at 11:49 PM, Nick Lewycky wrote:

> Bill Wendling wrote:
>> If I library allows information to be available outside of it, but doesn't give that code write permissions, then that would cause a failure.
>> 
>> This is what a linkedit segment is:
>> 
>> -seglinkedit
>>               Create  the  link edit segment, named ``__LINKEDIT'' (this is the default).  This segment con-
>>               tains all the link edit information (relocation information, symbol table, string table, etc.)
>>               in  the object file.  If the segment protection for this segment is not specified, the initial
>>               protection is not writable.  This can only be specified when  the  output  file  type  is  not
>>               MH_OBJECT  and MH_PRELOAD output file types.  To get at the contents of this section, the Mach
>>               header and load commands must be parsed from the link editor defined symbols  like  `__mh_exe-
>>               cute_header' (see Mach-O(5)).
>> 
>> More details here:
>> 
>> 	http://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/MachORuntime/Reference/reference.html
> 
> Hrm, I see. Carry on!
> 
> Thanks for the explanation!
> 
Sure. Sorry to be a bit vague. I'm trying to solve a rather difficult problem and making our stuff work similarly to how GCC's coverage works seems to be the best route to take here.

-bw






More information about the llvm-commits mailing list