Memory Analysis with size Command in C

[Kittu20]

How do we analyze the memory utilization of different sections such as text, data, and bss in a compiled binary file in C programming?

The size command on linux -systems provides information about the sizes of various sections. The output includes columns such as text, data, bss, dec, hex, and filename.

The text section represents the size of the code segment, which contains executable instructions.
The data section shows the size of initialized data variables, while the bss section indicates the size of uninitialized data variables

[audiotubes]

I don't know, does this help? https://en.wikipedia.org/wiki/Valgrind

[DiTBho]

You can search for documentation on "GNU binutils", there are specific tools and tutorial for this type of analysis 

[Nominal Animal]

How do we analyze the memory utilization of different sections such as text, data, and bss in a compiled binary file in C programming?

On systems like Linux that use ELF binaries (and thus almost certainly either binutils or compatible tools), using
    objdump -hw binary
or
    readelf -SW binary
or parsing the ELF file directly.  There are two formats: 32-bit and 64-bit.  Both formats have two variants depending on byte order (endianness): little-endian or big-endian.

The size command is part of binutils like objdump and readelf are and provides a concise summary, whereas objdump and readelf provide the exact details.  The two differ in their low-level implementation: objdump uses the Binary File Descriptor library (BFD), readelf does not.

[SiliconWizard]

I don't think the OP was waiting for answers, as they answer their own question. Kinda.