Salman Khilji
After I compile my program I need access to the debug symbols (addresses and tyeps). I use a modified version of objdump (from binutils) to get to the debug symbols. My application monitors the value of static variables without stopping the target application unlike a source line debugger which has to stop the application to look at the values of variables.
Even the unmodified latest version of objdump could not read the debug info generated by gcc 3.1. Haven't tried 3.2.
It would say something like "bad mangled name" when you tried to get objdump to read debug symbols generated by gcc. Someone told me that this was a problme in the past and would be in the future because binutils and gcc was maintained by different groups.
Have you tried applying your objdump modifications to the latest binutils. I am using 2.13.90.0.4 (from ftp.kernel.org) and "objdump -t 'progname'" where progname was built with gcc3.2, lists the symbols perfectly. One solution to the problem of binutils and gcc being out of step is to build them from the same source tree. I have never done this myself, but believe that it is frequently used when building a cross-compile toolchain.