This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/9232] utils.c:947: internal-error: virtual memory exhausted: can't allocate 4294967420 bytes.


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]