public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27962] New: Internal error when using binary from gdb.dwarf2/arr-stride.exp
Date: Mon, 07 Jun 2021 19:35:54 +0000	[thread overview]
Message-ID: <bug-27962-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27962
           Summary: Internal error when using binary from
                    gdb.dwarf2/arr-stride.exp
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: simark at simark dot ca
  Target Milestone: ---

I stumbled on this a bit randomly while trying to reproduce a failure.  With
the binary from gdb.dwarf2/arr-stride.exp, with current master:

$ ./gdb -nx -q --data-directory=data-directory
testsuite/outputs/gdb.dwarf2/arr-stride/arr-stride  -ex "print the_struct"
Reading symbols from testsuite/outputs/gdb.dwarf2/arr-stride/arr-stride...
$1 = {intfield = 1, arrayfield = {
/home/simark/src/binutils-gdb/gdb/value.c:851: internal-error: bool
value_contents_bits_eq(const value*, int, const value*, int, int): Assertion
`offset2 + length <= TYPE_LENGTH (val2->enclosing_type) * TARGET_CHAR_BIT'
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) 



(top-gdb) p offset2
$1 = 32
(top-gdb) p length
$2 = 32
(top-gdb) p TYPE_LENGTH (val2->enclosing_type)
$3 = 4
(top-gdb) p TARGET_CHAR_BIT
$4 = 8

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

             reply	other threads:[~2021-06-07 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 19:35 simark at simark dot ca [this message]
2021-06-07 19:38 ` [Bug gdb/27962] " simark at simark dot ca
2021-06-07 20:37 ` tromey at sourceware dot org
2021-06-08 21:33 ` simark at simark dot ca
2021-06-08 23:07 ` tromey at sourceware dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27962-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).