What are the differences between the normal symbol table, the dynamic symbol table, and the debugging symbol table?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What are the differences between the normal symbol table, the dynamic symbol table, and the debugging symbol table?
I've always been confused by symbols and what their exact meanings are. So what are they? Just function names and variables? And further, what are the exact differences between the normal symbol table, the dynamic symbol table, and the debugging symbol table
Where are you getting this information about normal, dynamic, and debugging tables? A symbol table is merely a cross reference between high level code and assembly language so that when you observe the code in mixed source/assembly or in the debugger, you use the symbol table to tell you where the references are.
Yes it is function names and variables, macros are not included because they are expanded in the pre-processor and substituted to become code segments.
The only differences are choosing to add debug symbols or strip symbols completely. The first way being verbose to include as much detail as possible, for debugging purposes, and the second way to make the executable small and efficient.
I was under the impression these tables existed in the binary somewhere? Am I wrong?
When the compiler is directed to provide debugging output it typically creates it using standard formats such as STABS, or DWARF, or something else. For instance Microsoft uses their own and generates PDB files. If you use GDB to compile a simple C file you'll see that it adds more information to the binary output file when you specify -g options for dwarf or gdb.
normal, dynamic, and debugging tables?
NORMAL: something most people are not.
it is what is used at all times.
DYNAMIC: created on the fly to be used in a normal manner
DEBUGGING: has symbols in it for use in debugging the table. raid is this case will not work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.