This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: _bfd_link_section_stabs: hash value weakness


Daniel Jacobowitz <drow@mvista.com> writes:

> I'm not sure how often this could ever work, in practice, in a large
> application.  The type numbers must depend on the include hierarchy. 
> If you look at the sample Paul posted, the difference is that one of
> them has an earlier header defining 'struct value' and the other has an
> earlier header just declaring 'struct value;' and leaving it at that. 
> Thus the "xs" stab, in evaluate_exp.

I think I agree with what you say, but I don't see why what you say is
a problem.  There are two possibilities I see: 1) you get a different
hash code, in which case the program is larger than necessary, but
detecting all such cases is very difficult; 2) the merge is done,
which may require the debugger to locate a different definition for
`struct value', but it must be prepared to do that in any case.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]