Question

See, the problem is that I’m supposed to use an executable driver program (vdriver) to test the C source file I wrote (myfile.c) containing a collection of methods the driver program will use. I used gcc to compile them together (and also any files they depend on) and then ran “gdb vdriver”

Apparently, I am getting a segfault somewhere in myfile.c. The “dissasemble”-produced assembly code can even display the whole method in assembly and point to which instruction just segfaulted.

However, due to the complexity (and length) of the assembly code, I think it would be much more effective to view this line where the segfault occurred in C.

However, running the command “list *$eip” results in:

    No source file for address 0x804a3d3

Does anyone know how to make this work?

Answer 1

Compile with debugging info.

gcc -ggdb -c source.c -o source.o ...

Update: It looks like you’re having trouble invoking GCC as well. I suggest writing a Makefile, and taking a quick look through the GCC manual for what -c and -o mean.

CC = gcc
CFLAGS = -ggdb -Wall # or whatever flags you want, read the manual

# List all files, with *.c changed to *.o (Make will figure the rest out)
my_app : file1.o file2.o file3.o file4.o
        $(CC) -o my_app $^
# The above line should start with a tab, not spaces

clean :
        rm -f my_app *.o

# List dependencies like this (technically optional)
# But if you don't do it, "make" might not re-make things that need it
file1.o : file1.c header.h header2.h
file2.o : file2.c header.h