public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "at_gdb at mathalacarte dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/18475] New: Crash on a print
Date: Mon, 01 Jun 2015 18:40:00 -0000	[thread overview]
Message-ID: <bug-18475-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 18475
           Summary: Crash on a print
           Product: gdb
           Version: 7.9
            Status: NEW
          Severity: normal
          Priority: P2
         Component: fortran
          Assignee: unassigned at sourceware dot org
          Reporter: at_gdb at mathalacarte dot com
  Target Milestone: ---

While running ddd 3.3.12 with gdb 7.9.1 on a Fortran program I encountered
this:

(gdb) p y(nv1:lrow)
cp-namespace.c:341: internal-error: cp_search_static_and_baseclasses: Assertion
`name[prefix_len + 1] == ':'' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

This is a bug, please report it.  For instructions, see:
<http://bugs.gentoo.org/>.

At this point nv1 and lrow can both be printed and nv1=8 and lrow=9
p y(8:9) prints results just fine.

Just tried a similar thing with a different variable having a name ending in 1
and got the same kind of crash.  Perhaps things are grouped like <nv><1:...
instead of <nv1><:...?

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


             reply	other threads:[~2015-06-01 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 18:40 at_gdb at mathalacarte dot com [this message]
2015-06-04  2:37 ` [Bug fortran/18475] "p y(nv1:lrow)" hits cp-namespace.c:341: internal-error: cp_search_static_and_baseclasses: Assertion `name[prefix_len + 1] == ':'' failed vapier at gentoo 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-18475-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).