Question

I am building a project that builds multiple shared libraries and executable files. All the source files that are used to build these binaries are in a single /src directory. So it is not obvious to figure out which source files were used to build each of the binaries (there is many-to-many relation).

My goal is to write a script that would parse a set of C files for each binary and make sure that only the right functions are called from them.

One option seems to be to try to extract this information from Makefile. But this does not work well with generated files and headers (due to dependence on Includes).

Another option could be to simply browse call graphs, but this would get complicated, because a lot of functions are called by using function pointers.

Any other ideas?

Answer 1

You can first compile your project with debug information (gcc -g) and use objdump to get which source files were included.

objdump -W <some_compiled_binary>

Dwarf format should contain the information you are looking for.

 <0><b>: Abbrev Number: 1 (DW_TAG_compile_unit)
    < c>   DW_AT_producer    : (indirect string, offset: 0x5f): GNU C 4.4.3 
    <10>   DW_AT_language    : 1    (ANSI C)
    <11>   DW_AT_name        : (indirect string, offset: 0x28): test_3.c    
    <15>   DW_AT_comp_dir    : (indirect string, offset: 0x36): /home/auselen/trials    
    <19>   DW_AT_low_pc      : 0x82f0   
    <1d>   DW_AT_high_pc     : 0x8408   
    <21>   DW_AT_stmt_list   : 0x0  

In this example, I’ve compiled object file from test_3, and it was located in …/trials directory. Then of course you need to write some script around this to collect related source file names.