illumos gate

I sound crazy, I know. I feel it as well.

Igor merged some ZFS changes, that include the definition of this variable:

static const zfs_ioc_key_t zfs_keys_remap[] = {
    /* no nvl keys */
};

For which his compiler generated the following DWARF:

< 1><0x0001b93e>    DW_TAG_array_type
                      DW_AT_type                  <0x0001b7bd>
                      DW_AT_sibling               <0x0001b94e>
< 2><0x0001b947>      DW_TAG_subrange_type
                        DW_AT_type                  <0x0001b953>
                        DW_AT_upper_bound           0xffffffffffffffff (-1)
< 1><0x0001b94e>    DW_TAG_const_type
                      DW_AT_type                  <0x0001b93e>
< 1><0x0001b95a>    DW_TAG_variable
                      DW_AT_name                  zfs_keys_remap
                      DW_AT_decl_file             0x00000001 /rws1/users/igor/dilos-illumos.zfs/usr/src/uts/intel/zfs/../../common/fs/zfs/zfs_ioctl.c
                      DW_AT_decl_line             0x00000d84
                      DW_AT_type                  <0x0001b94e>
                      DW_AT_location              DW_OP_addr 0x000004b0

which for reasons I don't understand, has an upper bound of -1. We assume that we can get DW_AT_upper_bound as unsigned, and thus fail.

A simple test case is:

struct yuck {
    int a;
    int b;
};

const struct yuck yucks[] = {
    /* no yucks to give */
};