Subject: Re: bug#66416: GDB output from new crash

From: Yuchen Guo <[email-masked]>
Date: Thu, 12 Oct 2023 14:28:54 +0000

Po Lu <[email-masked]> writes:

>   (gdb) p *ftcrfont_info
>
> should prove illuminating.
Output:

{font =
    {header = {size = 4611686018997895185},
     props = {0x7c50, 0x3e581280, 0x41493ef0, 0x0, 0x9870, 0x14102,
    0x19082, 0x19102, 0x6e, 0x0, 0x0, 0x2, 0x42277373, 0x0,
    0x40229f14, 0x40229ef4, 0x402299a4},
     min_width = 8,
     max_width = 29,
     pixel_size = 27,
     height = 39,
     space_width = 10,
     average_width = 15,
     ascent = 31,
     descent = 8,
     underline_thickness = 0,
     underline_position = 3,
     vertical_centering = false,
     baseline_offset = 0,
     relative_compose = 0,
     default_ascent = 0,
     encoding_charset = -1,
     repertory_charset = -1,
     driver = 0xc0ece0 <ftcrhbfont_driver>
    },
    ft_size = 0x0,
    index = 1072040480,
    matrix = {xx = 0, xy = 1109821571, yx = 5, yy = 0},
    hb_font = 0x0,
    cr_scaled_font = 0x4211a9e0,
    bitmap_position_unit = 0,
    metrics = 0x41412720,
    metrics_nrows = 10
    }