------- Additional Comments From divis1969 at gmail dot com 2008-08-14 10:10 ------- (In reply to comment #5) > If you run your ELF binary through "readelf -w" does it report any > problems with the debug information ?
Yes, a lot of. Like this: readelf: Warning: There is a hole [0xab1ea0 - 0xab2551] in .debug_loc section. readelf: Warning: There is an overlap [0xab25ab - 0xab1ea0] in .debug_loc sectio n. > Without a test case and a procedure to follow to reproduce the bug, I > really do not think that we are going to be able to solve this > problem. Are you sure that you cannot provide us with an ELF file ? > You could always zero out the proprietary information first before > uploading it. I'm afraid I will need to remove whole debug info in order to remove this proprietary info. I suppose, it is possible to generate such an ELF using GCC. I've described the conditions it has to meet. > I think that would be the wrong way to fix the problem. It would mean > that the stash pointer passed to comp_unit_find_line would be > incorrect. Maybe. Though, I believe it is also useless to pass the pointer above this section. I think this value is not used at all except handling DW_AT_abstract_origin. Dmitry -- http://sourceware.org/bugzilla/show_bug.cgi?id=6832 ------- 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
