public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug ada/28323] New: segfault in ada_is_unconstrained_packed_array_type
Date: Thu, 09 Sep 2021 14:10:43 +0000	[thread overview]
Message-ID: <bug-28323-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28323
           Summary: segfault in ada_is_unconstrained_packed_array_type
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ada
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With test-case rtf=gdb.ada/mi_dyn_arr.exp I run into a segfault on openSUSE
Leap 42.3 with gcc-4.8:
...
(gdb) ^M
Expecting: ^(-var-create bt \* bt[^M
]+)?(\^done,name="bt",numchild="3",.*[^M
]+[(]gdb[)] ^M
[ ]*)
-var-create bt * bt^M
ERROR: Process no longer exists
UNRESOLVED: gdb.ada/mi_dyn_arr.exp: create bt varobj
ERROR: Couldn't send -var-update 1 * to GDB.
...

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

             reply	other threads:[~2021-09-09 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 14:10 vries at gcc dot gnu.org [this message]
2021-09-09 14:33 ` [Bug ada/28323] " vries at gcc dot gnu.org
2021-09-09 14:53 ` vries at gcc dot gnu.org
2021-09-09 14:59 ` vries at gcc dot gnu.org
2021-12-06 12:14 ` vries at gcc dot gnu.org
2021-12-07  6:36 ` vries at gcc dot gnu.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-28323-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).