Question

I’m trying to debug an issue where the wrong version of a function gets called causing a segfault. The code that I’m compiling is machine generated and includes a function called ‘times’ that does a complex multiply of it’s two arguments. This code is compiled to a .o before being linked into a higher level object file.

When run this code segfaults and gdb indicates that it’s in glibc’s version of ‘times’ which doesn’t even take the same number of arguments. The are no instances of ‘#include anywhere in this code.

Changing the name of times to times1 resolves the problem. This isn’t a long term solution though due to the machine generated nature of the code and manually editing the name of this function all the time is unappealing.

The whole mess compiles cleaning with -Wall so I’m not sure where to look. Any ideas on how to resolve this?

Compile chain:
    gcc -Wall -I. -g --shared -o dpd.o -fPIC *.c (mahine generated code here)
    gcc -g --std=c99 -c -fpic getData.c -I/usr/local/include -L/usr/local/lib -lmatio -I/usr/local/include/iverilog -I$(MATLAB)
    gcc -g -shared -o getData.vpi getData.o $(MATLAB)/dpd.o -lvpi -lmatio -L/usr/local/lib

Answer 1

So the real answer to this one is to throw -fno-builtin-times to gcc. That avoids the problem neatly with no fuss.

This of course assumes that you can’t changes the name of times to something that doesn’t conflict with a glibc provided function.