to clarify, my question refers to wrapping/intercepting calls from one function/symbol to another function/symbol when the caller and the callee are defined in the same compilation unit with the GCC compiler and linker.
I have a situation resembling the following:
/* foo.c */
void foo(void)
{
/* ... some stuff */
bar();
}
void bar(void)
{
/* ... some other stuff */
}
I would like to wrap calls to these functions, and I can do that (to a point) with ld's --wrap
option (and then I implement __wrap_foo and __wrap_bar which in turn call __real_foo and __real_bar as expected by the result of ld's --wrap
option).
gcc -Wl,--wrap=foo -Wl,--wrap=bar ...
The problem I'm having is that this only takes effect for references to foo and bar from outside of this compilation unit (and resolved at link time). That is, calls to foo and bar from other functions within foo.c do not get wrapped.
I tried using objcopy --redefine-sym, but that only renames the symbols and their references.
I would like to replace calls to foo
and bar
(within foo.o) to __wrap_foo
and __wrap_bar
(just as they get resolved in other object files by the linker's --wrap
option) BEFORE I pass the *.o files to the linker's --wrap
options, and without having to modify foo.c's source code.
That way, the wrapping/interception takes place for all calls to foo
and bar
, and not just the ones taking place outside of foo.o.
Is this possible?
You can use
__attribute__((weak))
before the implementation of the callee in order to let someone reimplement it without GCC yelling about multiple definitons.For example suppose you want to mock the
world
function in the following hello.c code unit. You can prepend the attribute in order to be able to override it.And you can then override it in another unit file. Very useful for unit testing/mocking:
And then just compile this code and debug. When you call the reall malloc, the function called will __wrap_malloc and __real_malloc will call malloc.
I think this is the way to intercept the calls.
Basically its the --wrap option provided by ld.
You can achieve what you want if you use
--undefined
with--wrap
This appears to be working as documented:
Note the undefined above. When the linker processes
foo.o
, thebar()
is not undefined, so the linker does not wrap it. I am not sure why it's done that way, but there probably is a use case that requires this.You have to weaken and globalize the symbol using objcopy.
This worked for me
bar.c:
foo.c:
Compile it
Weaken the foo symbol and make it global, so it's available for linker again.
Now you can link your new obj with the wrap from bar.c
Test
And the wrapped one: