When I tried to debug an executable:
(gdb) break +1
No symbol table is loaded. Use the "file" command.
What does that mean exactly?
Is the symbol table appended to the executable?
views:
310answers:
3
+1
A:
It's because you didn't compile with debugging turned on. Try gcc -g file.c
rkulla
2010-04-05 05:39:54
Do you mean gdb can't be used to debug arbitary programe?
2010-04-05 05:40:58
@user198729: You can use GDB to debug an arbitrary program, but you have to work a lot harder if the program does not have a symbol table. Basically, the symbol table tells the debugger about the functions and variables and line numbers and source files - and if it is missing, all you've got left is assembler.
Jonathan Leffler
2010-04-05 05:51:52
@Jonathan Leffler,it seems you mean it's still possible to debug the program even if it doesn't have a symbol table,can you give an example?
2010-04-05 05:56:22
I mean it is very tough - tough enough that I wouldn't bother to try. But there are those who work in assembler and can debug an arbitrary program. I think they're mad, but they're probably also better programmers than me - in some respects, at least. You end up stepping through the code one assembler instruction at a time.
Jonathan Leffler
2010-04-05 06:33:01
+1
A:
The symbol table contains debugging information that tells a debugger what memory locations correspond to which symbols (like function names and variable names) in the original source code file. The symbol table is usually stored inside the executable, yes.
gdb is telling you that it can't find that table. If you compiled with gcc, unless you used the -g flag, it will not include the symbol table in the file. The easiest method is probably to recompile your file with -g. gdb should then automatically find the symbol table information.
Either add the -g flag to the command line arguments of gcc or to the Makefile that you used to compile the program. (A lot of times, there will be a variable called CFLAGS or similar inside the Makefile).
If you are trying to debug an arbitrary third-party program, a lot of times the information will have been "stripped" out of it. This is done to make reverse engineering harder and to make the size of the executable file smaller. Unless you have access to the source code and can compile the program yourself, you will have a very hard time using gdb on it.
RarrRarrRarr
2010-04-05 05:44:58
Why some other tools like softice can debug arbitrary program,aren't they using the same techniques as gdb?
2010-04-05 05:54:21
Roughly the same techniques, yes. You can do similar things with gdb like put breakpoints on system calls or examine assembly code or look at register values or contents of specific memory addresses, even without a symbol table. You may also want to check out strace or ltrace if you are on Linux.
RarrRarrRarr
2010-04-05 05:59:31
But no matter what command I type,gdb always responds with `No symbol table is loaded. Use the "file" command.`,it seems impossible for it to debug a program without symbol table..Or maybe there is something I'm missing out?
2010-04-05 06:07:54
@user198729: with no symbol table, you cannot do symbolic debugging. You have to include the correct compilation options when creating the object files and when linking - most often, that is '`-g`' for both object generation and linking. You must also not specify '`-s`' (strip), nor must you subject the program to '`strip`'.
Jonathan Leffler
2010-04-05 06:55:59
+1
A:
There are two sets of symbols that gdb uses.
The -g set are debugging symbols, which make things a lot easier as they allow you to see your code and look at variables while debugging.
Another set of symbols is included by default when you compile. These are the linking symbols and live in the ELF (executable linkable format) symbol table. This contains a lot less info than the debug symbols, but contain the most important stuff, such as the addresses of the things in your executable (or library or object file). Without this information gdb won't even know where main is, so (gdb) break main would fail.
If you don't have the debugging symbols ( -g ) then you will still be able to (gdb) break main but you gdb will not have any concept of the lines of code in your source file. When you try to step through the code you will only advance 1 machine instruction at a time, rather than a line at a time.
The strip command is often used to strip off symbols from an executable (or other object file).
This is often used if you don't want someone to be able to see the symbols or if you want to save space in the file. Symbol tables can get big. Strip removes both the debug symbols and the linker symbols, but it has several command line switches which can limit what it removes.
If you run the file command on your program one of the things it will tell you is weather or not the executable is has been stripped.
$ gcc my_prog.c -o my_prog
$ file my_prog
my_prog: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped
$ strip my_prog
my_prog: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
$
nategoose
2010-04-05 06:11:27