[Bug gdb/26861] internal-error: void target_mourn_inferior(ptid_t): Assertion `ptid == inferior_ptid' failed. OS: Mac OSX Catalina; Compiler: GCC; Language: C

["mehmetgelisin at aol dot com" <sourceware-bugzilla@sourceware.org>]

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

Mehmet gelisin <mehmetgelisin at aol dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mehmetgelisin at aol dot com

--- Comment #28 from Mehmet gelisin <mehmetgelisin at aol dot com> ---
I received the following error messages: https://komiya-dental.com/ 
../../gdb/target.c:2149: internal-error: void target_mourn_inferior(ptid_t):
Assertion `ptid == inferior_ptid' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session  http://www.iu-bloomington.com/ 
I received the following error messages:
../../gdb/target.c:2149: internal-error: void target_mourn_inferior(ptid_t):
Assertion `ptid == inferior_ptid' failed. https://www.webb-dev.co.uk/ 
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session $ cat test.c
        struct foo {
            int len; https://waytowhatsnext.com/ 
            int items[];
        };

        struct foo *p; http://www.acpirateradio.co.uk/

        int main() {
            return 0;
        }
        $ gcc test.c -g -O0 -o test http://www.logoarts.co.uk/
        $ ./gdb -q -nx --data-directory=data-directory ./test -ex 'python
gdb.parse_and_eval("p").type.target()["items"].type.range()'
http://www.logoarts.co.uk/ 
        Reading symbols from ./test...
        /home/simark/src/binutils-gdb/gdb/gdbtypes.h:435: internal-error:
LONGEST dynamic_prop::const_val() const: Assertion `m_kind == PROP_CONST'
failed. http://www.slipstone.co.uk/ 
        A problem internal to GDB has been detected,
        further debugging may prove unreliable.
        Quit this debugging session? (y or n) http://embermanchester.uk/ 

    This is because the Python code (typy_range) blindly reads the high
    bound of the type of `items` as a constant value.  Since it is a
    flexible array member, it has no high bound, http://connstr.net/  the
property is undefined.
    Since commit 8c2e4e0689 ("gdb: add accessors to struct dynamic_prop"),
    the getters http://joerg.li/  check that you are not getting a property
value of the wrong
    kind, so this causes a failed assertion.

    Fix it by checking if the property http://www.jopspeech.com/  is indeed a
constant value before
    accessing it as such.  Otherwise, use 0.  This restores the previous GDB
    behavior:  because the structure was zero-initialized,
http://www.wearelondonmade.com/ this is what was 
    returned before.  But now this behavior is explicit and not accidental.

    Add a test, http://www.compilatori.com/
gdb.python/flexible-array-member.exp, that is derived from
    gdb.base/flexible-array-member.exp.  It tests the same things, but
    through the Python API.  It also specifically tests getting the range
    from the various kinds of flexible array member types (AFAIK it wasn't
    possible to do the equivalent through the CLI). http://www-look-4.com/

    gdb/ChangeLog:

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