[Bug breakpoints/28018] internal-error: Assertion 'TYPE_LENGTH(index_type) > 0' failed in create_range_type

["kadler at us dot ibm.com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=28018

--- Comment #12 from Kevin Adler <kadler at us dot ibm.com> ---
> DWARF keeps some data associated to each compunit_symtab on the side, in the
> dwarf2_per_objfile::m_symtabs field.  It sounds like you would need something 
> like that.  When symtab 2 depends on a type in symtab 1, then you could lookup 
> symtab 1's type vector in that per-compunit_symtab data.  Or maybe I completely > misunderstand the problem.

Yeah, I think something like this will be necessary. I actually found a patches
the AIX team has in their build of GDB 8.1 that does something like this. That
was to address issues when using --function-sections/-qfuncsect, which makes
this problem worse by putting every function in to its own csect.

BTW, I actually confused myself initially. While we _are_ failing to look up
the element type of the array, the assertion is not on that type, but on the
type used to index the array. I didn't even realize that could or needed be
specified.  :) One hack around the assertion problem would be to check if we
got an undefined type when looking up the index type and in that case override
the type using the builtin type for unsigned long. Of course, that wouldn't fix
the larger issue and so the element type of the array would still be undefined.

-- 
You are receiving this mail because:
You are on the CC list for the bug.