@shegeley do you mean GDB will not load the debugging symbols for your C program? I assume your are building a dynamically linked library with the GCC "-fPIC -shared" options?
So I don't think ".so" files contain debug symbols unless you also pass the "-ggdb" option. I can't remember well, but I think it is something like:
> "i mean how to I run gcc with guile script and get symbols for it in a sigsegv backtrace"
@shegeley you should make sure that the ".so" files being loaded by Guile have their debugging symbols available. If for example you are linking against "libgtk-3.so" and the crash occurs in this file, the symbol table is probably not available unless you install those from your package manager, or build the whole Gtk3 library yourself with the "-g" flag included in your "CC_FLAGS" environment setting when running the "./configure" autoconf script for Gtk.
I am pretty sure you can accomplish this with the Guix package manager, but I am not sure exactly how.
> "i mean how to I run gcc with guile script and get symbols for it in a sigsegv backtrace"
@shegeley you should make sure that the ".so" files being loaded by Guile have their debugging symbols available. If for example you are linking against "libgtk-3.so" and the crash occurs in this file, the symbol table is probably not available unless you install those from your package manager, or build the whole Gtk3 library yourself with the "-g" flag included in your "CC_FLAGS" environment setting when running the "
@shegeley do you mean GDB will not load the debugging symbols for your C program? I assume your are building a dynamically linked library with the GCC "
-fPIC -shared
" options?So I don't think ".so" files contain debug symbols unless you also pass the "
-ggdb
" option. I can't remember well, but I think it is something like:Here is the relevant section of the GCC manual.