https://sourceware.org/bugzilla/show_bug.cgi?id=24984

--- Comment #4 from Grzegorz Antoniak <antonone+sourceware at gmail dot com> ---
Okay, I understand that ".bss" has a non-zero virtual size, and a zero physical
size (that means, there is no file data inside the file for this section).

But when I mark ".CustomData" as no-content, I'm ending up having the file
content in my executable file, consisting of 0x00 bytes. My binary has a ~500mb
size. Most of this space is assigned to a section which is marked as
no-content. So ".CustomData" has a non-zero virtual size and a non-zero
physical size while being marked as no-content.

Shouldn't ".CustomData" be build like ".bss" is built when I don't specify the
"content" flag? So, shouldn't it be just a section declaration in the section
header without the actual space reservation in the executable file? Because
currently the physical space reservation for this section exists in the file.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils

Reply via email to