Displaying 2 results from an estimated 2 matches for "__unwind_info".
2019 May 23
3
Proposal for Mach-O support in llvm-objcopy: section renaming
...nd that’s basically the proposal here. So while not ideal, it’s certainly familiar.
How will people use llvm-objcopy when the segment and section names legitimately contain “.” or “,” characters? Will these be escapable?
The rest of the behavior, especially around “__TEXT.__text is bad but __TEXT.__unwind_info is good”, is pretty confusing. Can we define our own “canonical names” for canonical sections such as __unwind_info?
>
> Thanks,
>
> James
>
> On Thu, 23 May 2019 at 05:43, Seiya Nuta <nuta at seiya.me <mailto:nuta at seiya.me>> wrote:
> Hi,
>
> I'm...
2019 May 23
2
Proposal for Mach-O support in llvm-objcopy: section renaming
...quot;canonical" name [2].
- Otherwise:
- Rename to "<segment name>.<section name>" (the separator is `.' not `,')
- If the segment name does not start with `_', prefix it with `LC_SEGMENT.'
For example, __TEXT,__text is renamed to .text and
__TEXT,__unwind_info is renamed to __TEXT.__unwind_info. For that
reason, specifying a section in command line options is rather
nonintuitive:
WRONG: objcopy --only-secton=__TEXT,__text a.out
WRONG: objcopy --only-secton=__TEXT.__text a.out
OK: objcopy --only-secton=.text a.out
WRONG: objcopy --only-secton=__TEXT,__u...