[Bug corefiles/18964] New: [mips] 7.9 regression: internal-error: mips-tdep.c:1098: bad register size

[Bug corefiles/18964] New: [mips] 7.9 regression: internal-error: mips-tdep.c:1098: bad register size

[jan.kratochvil at redhat dot com]

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

            Bug ID: 18964
           Summary: [mips] 7.9 regression: internal-error:
                    mips-tdep.c:1098: bad register size
           Product: gdb
           Version: 7.9
            Status: NEW
          Severity: normal
          Priority: P2
         Component: corefiles
          Assignee: unassigned at sourceware dot org
          Reporter: jan.kratochvil at redhat dot com
                CC: arnez at linux dot vnet.ibm.com, jan.kratochvil at redhat dot com
        Depends on: 17808
  Target Milestone: ---
            Target: x86_64-linux-gnu

+++ This bug was initially created as a clone of Bug #17808 +++

Expected output on a MIPS host:

./gdb -q -c ./i386-biarch-core.core 
gdb/mips-tdep.c:1098: internal-error: bad register size

core-file gdb.arch/i386-biarch-core.core
gdb/mips-tdep.c:1098: internal-error: bad register size
A problem internal to GDB has been detected,
further debugging may prove unreliable.^
Quit this debugging session? (y or n)
FAIL: gdb.arch/i386-biarch-core.exp: core-file (GDB internal error)

Probably:
8f0435f75e3c9676d2e177ce055fed3155fd9476 is the first bad commit
commit 8f0435f75e3c9676d2e177ce055fed3155fd9476
Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Date:   Fri Sep 12 08:42:48 2014 +0000
    Add 'regset' parameter to 'iterate_over_regset_sections_cb'
Message-Id: <1410538439-29791-1-git-send-email-arnez@linux.vnet.ibm.com>


Referenced Bugs:

https://sourceware.org/bugzilla/show_bug.cgi?id=17808
[Bug 17808] 7.9 regression: internal-error: i386_supply_gregset: Assertion `len
== tdep->sizeof_gregset' failed.
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug corefiles/18964] [mips] 7.9 regression: internal-error: mips-tdep.c:1098: bad register size

[jan.kratochvil at redhat dot com]

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

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |luis_gustavo at mentor dot com

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

[Bug corefiles/18964] [mips] 7.9 regression: internal-error: mips-tdep.c:1098: bad register size

[arnez at linux dot vnet.ibm.com]

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

--- Comment #1 from Andreas Arnez <arnez at linux dot vnet.ibm.com> ---
(In reply to Jan Kratochvil from comment #0)
> +++ This bug was initially created as a clone of Bug #17808 +++
> 
> Expected output on a MIPS host:
> 
> ./gdb -q -c ./i386-biarch-core.core 
> gdb/mips-tdep.c:1098: internal-error: bad register size

What version is this?  I don't see this assertion near line 1098 in upstream
GDB or GDB 7.9.1.

And do you have more information?  A full backtrace might be helpful.  I don't
have a MIPS host, so I can't reproduce this bug.

> Probably:
> 8f0435f75e3c9676d2e177ce055fed3155fd9476 is the first bad commit

Hm, nothing obvious here.  The patch doesn't directly touch the MIPS target
support.

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

[Bug corefiles/18964] [mips] 7.9 regression: internal-error: mips-tdep.c:1098: bad register size

[lgustavo at codesourcery dot com]

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

Luis Machado <lgustavo at codesourcery dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lgustavo at codesourcery dot com

--- Comment #2 from Luis Machado <lgustavo at codesourcery dot com> ---
The lines don't match because i have a slightly modified version of the
sources. I'll give it a try with unmodified upstream sources, but the code is
basically the same for that function.

I didn't investigate this further, but i suppose this is a missing adjustment
in mips-tdep.c rather than something that was broken by another commit.

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

[Bug corefiles/18964] [mips] 7.9 regression: internal-error: mips-tdep.c:1098: bad register size

[lgustavo at codesourcery dot com]

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

--- Comment #3 from Luis Machado <lgustavo at codesourcery dot com> ---
Also, this is what i mentioned in the list post...

"The lines are a bit off, but basically we end up hitting the internal error at
mips-tdep.c:mips_pseudo_register_read. I don't think the MIPS backend is
currently crafted to handle reading unknown register blocks."

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

[Bug corefiles/18964] [mips] 7.9 regression: internal-error: mips-tdep.c:1098: bad register size

[palves at redhat dot com]

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

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at redhat dot com

--- Comment #4 from Pedro Alves <palves at redhat dot com> ---
This being a -tdep.c file, you probably don't need a mips-hosted gdb.

A --target=mips-linux-gnu build probably suffices.

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

[Bug corefiles/18964] [mips] 7.9 regression: internal-error: mips-tdep.c:1098: bad register size

[arnez at linux dot vnet.ibm.com]

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

--- Comment #6 from Andreas Arnez <arnez at linux dot vnet.ibm.com> ---
(In reply to Jan Kratochvil from comment #0)
> Probably:
> 8f0435f75e3c9676d2e177ce055fed3155fd9476 is the first bad commit
Note that I can't confirm this in my testing (see comment #5).  Instead, I see
the same problem with the parent of that commit.

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