[Bug gdb/26393] gdbtypes.h:526: internal-error: LONGEST dynamic_prop::const_val() const: Assertion `m_kind == PROP_CONST' failed. (recursive_dump_type)

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=53d5a2a5c146f98dd525eda2f33d7781666463bf

commit 53d5a2a5c146f98dd525eda2f33d7781666463bf
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon Aug 17 09:54:37 2020 +0200

    [gdb] Fix printing of unresolved dynamic type

    When debugging gdb in batch mode with executable mixed-lang-stack and doing
a
    backtrace at breakpt:
    ...
    $ gdb --args gdb \
      -batch \
      outputs/gdb.fortran/mixed-lang-stack/mixed-lang-stack \
      -ex "b breakpt" \
      -ex r \
      -ex bt
    ...
    and stopping at resolve_dynamic_type to print the type:
    ...
    (gdb) b resolve_dynamic_type
    Breakpoint 1 at 0x6b020c: file gdbtypes.c, line 2633.
    (gdb) commands
    Type commands for breakpoint(s) 1, one per line.
    End with a line saying just "end".
    >call recursive_dump_type (type, 0)
    >continue
    >end
    (gdb) run
    ...
    we eventually run into an assert for the dynamic type of "str":
    ...
    Thread 1 "gdb" hit Breakpoint 1, resolve_dynamic_type (type=0x22204f0, \
      valaddr=..., addr=4199408) at gdbtypes.c:2633
    2633        = {check_typedef (type), valaddr, addr, NULL};
    type node 0x22204f0
    name '<NULL>' (0x0)
    code 0xd (TYPE_CODE_STRING)
    length 0
      ...
        nfields 0 0x22204b0
    gdbtypes.h:526: internal-error: LONGEST dynamic_prop::const_val() const: \
      Assertion `m_kind == PROP_CONST' failed.
    A problem internal to GDB has been detected,
    further debugging may prove unreliable.
    ...
    when trying to print the high bound of a TYPE_CODE_RANGE, which has m_kind
    PROP_LOCEXPR, while the code in resolve_dynamic_type assumes PROP_CONST.

    Fix this by extending the printing of TYPE_CODE_RANGE to allow
    PROP_LOCEXPR/PROP_LOCLIST as well, such that we have instead:
    ...
        nfields 0 0x1fbc020
        low 1  high (dynamic)
    ...

    Tested on x86_64-linux.

    gdb/ChangeLog:

    2020-08-17  Tom de Vries  <tdevries@suse.de>

            PR gdb/26393
            * gdbtypes.c (dump_dynamic_prop): New function.
            (recursive_dump_type): Use dump_dynamic_prop for TYPE_CODE_RANGE.

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