how objdump handles global variables

Question

I have made the following dummy code for testing

/tmp/test.c contains the following:

#include \"test.h\"
#include 
#include 

        

Answer 1

The .o file is not yet executable, there'll be relocation entries pointing to those 0's which the linker will fixup later. Since your source file seems mostly self-contained, can you drop the -c flag to produce an (fully linked) executable rather than a relocatable object file?