Home/ Questions/Q 6729647
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T10:18:55+00:00

I’ll try to simplify and make clear my other question here. I am basically

  • 0

I’ll try to simplify and make clear my other question here. I am basically trying to use gdb to see where myfile.c is segfaulting. However, I cannot directly examine myfile.c under gdb, but there I am given a driver program (vdriver) that will randomly test the methods I have provided for it in myfile.c

So, after compiling with “gcc -ggdb -c vdriver.c myfile.c myfile_depends_on_this.c” I run “gdb vdriver” until it segfaults. At that point, typing “list *$eip” just prints “No source file for address 0x804something”

I am also confused about how I should “gcc -ggdb -c etc,etc” for header files such as myfile.h and myfile_depends_on_this.h, because I’m not sure whether (or how) it should be included in the command or not.

But anyway, is there any way of fixing the “No source file for address” problem?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Here is how I understand your question (it’s not quite clear to me):

    1. how to debug after a segfault?
    2. how to compile .h files?

    As to

    1. After crashes, you will no longer be in execution context and so no longer be able to use the regular debugging commands. Instead, gcc will produce a core file. You probably need to allocate space for a core file first, then debug, as described in (eg):

      http://www.network-theory.co.uk/docs/gccintro/gccintro_38.html

    2. .h files are not included in the list of files to be compiled. They are referenced from within your .c file with the usual #include (or #include “file.h”) semantic

    If this wasn’t your question, kindly elaborate.

    • 0