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. I tried all versions till 3.1 when I gave up on it and decided to stick with 2.95.3. That was one of the reasons I dumped Mandrake 8.0 and switched to SuSE 8.0. I won't switch for a long time to any newer version till they get evertying straigthen out with gcc. Salman On Sunday 15 September 2002 11:43, Mads Martin Joergensen wrote:
* Salman Khilji
[Sep 15. 2002 03:22]: Plus I don't want to upgrade becuase 8.1 is not going to have gcc 2.95.3. I don't want to downgrade to gcc 3.x since the stuff that I need is broken on all versions of 3.x that I have worked with. (Last time I tested was 3.1...haven't tried with 3.2).
What are these things? We've ported a lot of applications, so it could be the apps. you're mentioning is among them, and the fix just needs to be sent upstream.