public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/9232] utils.c:947: internal-error: virtual memory exhausted: can't allocate 4294967420 bytes.
Date: Wed, 24 Apr 2013 20:00:00 -0000 [thread overview]
Message-ID: <bug-9232-4717-tYUQUo25AK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9232-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=9232
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sergiodj at redhat dot com
--- Comment #9 from Sergio Durigan Junior <sergiodj at redhat dot com> 2013-04-24 20:00:22 UTC ---
(In reply to comment #8)
> (In reply to comment #7)
> > I'm not getting failures now, but the following seems a little strange to me.
> > I have stopped at the return on line 12. And ...
> >
> > (gdb) p ii(1:5)
> > slice out of range
> > (gdb) p ii(1)@5
> > $6 = (1, 2, 3, 4, 5)
> >
> > Perhaps this is considered normal?
>
> I don't know -- I don't know Fortran :)
> The usual rule is that gdb should follow the language rules.
> So if that is valid Fortran then I think it is a bug.
I don't know Fortran either, but I found the following page:
<https://www.mcs.anl.gov/~itf/dbpp/text/node84.html>
which uses and explains the concept. So I believe it is valid Fortran, yes.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-04-24 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9232-4717@http.sourceware.org/bugzilla/>
2013-04-12 17:02 ` tromey at redhat dot com
2013-04-12 17:26 ` at_gdb at mathalacarte dot com
2013-04-12 19:34 ` tromey at redhat dot com
2013-04-24 20:00 ` sergiodj at redhat dot com [this message]
2013-11-30 7:53 ` sharmafrequent at gmail dot com
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-9232-4717-tYUQUo25AK@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).