------- Additional Comments From nickc at redhat dot com 2006-08-08 09:54 ------- Hi Tan,
Sorry for taking so long to get back to this issue. I am afraid I will not be able to visit you in Santa Clara since I am currently living in the UK... So, perhaps you can do some investigation for me ? If I understand correctly the problem is that if you link your "medusa" application using SUN's linker you get an executable that is able to dynamically load the "my.so" library but which cannot be debugged by GDB because GDB complains about corrupted debug info. On the other hand if you link "medusa" using the binutils linker you can then debug the executable with GDB(*), but it is no longer able to dynamically load "my.so". Is this correct ? (*) Apart from not being able to break into routines in header files which I think is a completely separate issue. If this is right, then what we need to do is to find out how the two different versions of the executable differ. Can you examine them using the "readelf" program ? Does that show any obvious differences in the symbol table, program headers or section headers ? (Also does readelf give you any more information about the corrupt debug info ?) Cheers Nick -- http://sourceware.org/bugzilla/show_bug.cgi?id=2750 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
