Skip to main content
Reverse Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • But the section names would not be in the .exe anymore. AFAIK they get all merged and the sole point of the .CRT section along with the respective $-specifiers is to influence ordering of objects at link time. Commented Nov 11, 2022 at 9:13
  • @blabb this is really more commentary than an answer. And I really appreciate and enjoy reading your answers normally. I agree with rce that from the context it's clear this must be an object file and that it's likely MSVC-specific. Commented Nov 11, 2022 at 9:16
  • 2
    as the linked article says .crtcxu is likely to be placed at the end after .crtcxa ... and normally these labels that would be visible on object file disassembly tend to disappear in binary ( i see this notion is contradicted in comment ) try compiling the code in linked article the whole .crtcxu section which will be visible in object file iwill disappear after linking into binary Commented Nov 11, 2022 at 13:03
  • I merely meant to point out that the section names may change within the .exe, not that the object file wouldn't contain the original names. It was more aimed at the comment from @rce. Commented Dec 11, 2022 at 20:30