Re: fortran/2127: utils.c:947: internal-error: virtual memory exhausted: can't allocate 4294967420 bytes.

Re: fortran/2127: utils.c:947: internal-error: virtual memory exhausted: can't allocate 4294967420 bytes.

[Fred Krogh]

The following reply was made to PR fortran/2127; it has been noted by GNATS.

From: Fred Krogh <fkrogh@mathalacarte.com>
To: gdb-gnats@sources.redhat.com,  nobody@sources.redhat.com, 
 fkrogh@mathalacarte.com,  gdb-prs@sources.redhat.com
Cc:  
Subject: Re: fortran/2127: utils.c:947: internal-error: virtual memory exhausted:
 can't allocate 4294967420 bytes.
Date: Wed, 31 May 2006 12:08:02 -0700

 http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=2127
 
 Just checked on this after another crash, and discovered that I had not
 used a 6.5 prerelease, even though at that time I thought I had the
 latest prerelease.  I just tried the current latest and have exactly the
 same problem.  /usr/local/bin/gdb --version gives
 
 GNU gdb 6.5.50.20060529-cvs
 ...

Re: fortran/2127: utils.c:947: internal-error: virtual memory exhausted: can't allocate 4294967420 bytes.

[Fred Krogh]

The following reply was made to PR fortran/2127; it has been noted by GNATS.

From: Fred Krogh <fkrogh@mathalacarte.com>
To: gdb-gnats@sources.redhat.com,  fkrogh@mathalacarte.com, 
 gdb-prs@sources.redhat.com
Cc:  
Subject: Re: fortran/2127: utils.c:947: internal-error: virtual memory exhausted:
 can't allocate 4294967420 bytes.
Date: Wed, 07 Jun 2006 16:49:26 -0700

 http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=2127
 
 I've just installed gfortran which was recently unmasked in Gentoo.  The
 problem is not present when using GNU Fortran 95 (GCC) 4.1.1 (Gentoo
 4.1.1). Just in case, if anyone knows what needs to be said to get ddd
 to display part of an array or all or part of a dummy array, I'd love to
 know the incantation.  Printing works, display doesn't except for a
 display of all of an array that is not a formal argument. Thanks,
 Fred

Re: fortran/2127: utils.c:947: internal-error: virtual memory exhausted: can't allocate 4294967420 bytes.

[Fred Krogh]

The following reply was made to PR fortran/2127; it has been noted by GNATS.

From: Fred Krogh <fkrogh@mathalacarte.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-gnats@sources.redhat.com
Subject: Re: fortran/2127: utils.c:947: internal-error: virtual memory exhausted:
 can't allocate 4294967420 bytes.
Date: Thu, 18 May 2006 09:38:12 -0700

 Daniel Jacobowitz wrote:
 > On Thu, May 18, 2006 at 01:42:29PM -0000, fkrogh@mathalacarte.com wrote:
 >   
 >> p (*ii)(3)
 >> gives a fatal error.
 >>
 >> The problem is probably due to II being declared with a dimension of *.
 >>     
 >
 > Could you please try a GDB 6.5 prerelease?  I'm not sure, but I believe
 > Wu fixed this problem.
 >
 >   
 Just checked with GNU gdb 6.4.50.20060515-cvs
 and got exactly the same problem.
 Thanks,
    Fred

Re: fortran/2127: utils.c:947: internal-error: virtual memory exhausted: can't allocate 4294967420 bytes.

[Daniel Jacobowitz]

The following reply was made to PR fortran/2127; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@false.org>
To: fkrogh@mathalacarte.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: fortran/2127: utils.c:947: internal-error: virtual memory exhausted: can't allocate 4294967420 bytes.
Date: Thu, 18 May 2006 09:49:25 -0400

 On Thu, May 18, 2006 at 01:42:29PM -0000, fkrogh@mathalacarte.com wrote:
 > p (*ii)(3)
 > gives a fatal error.
 > 
 > The problem is probably due to II being declared with a dimension of *.
 
 Could you please try a GDB 6.5 prerelease?  I'm not sure, but I believe
 Wu fixed this problem.
 
 -- 
 Daniel Jacobowitz
 CodeSourcery

fortran/2127: utils.c:947: internal-error: virtual memory exhausted: can't allocate 4294967420 bytes.

[fkrogh]

>Number:         2127
>Category:       fortran
>Synopsis:       utils.c:947: internal-error: virtual memory exhausted: can't allocate 4294967420 bytes.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 18 13:48:01 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Fred Krogh
>Release:        6.4
>Organization:
>Environment:
Gentoo Linux, gdb-6.4-r4, dual Opteron, GNU Fortran (GCC) 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)
>Description:
test.f is attached.
g77 -g -o test test.f
gdb test
b test.f:12
run
p ii(3)
or
p (*ii)(3)
gives a fatal error.

The problem is probably due to II being declared with a dimension of *.

This problem has a terrible side effect when using ddd.  If when moving the mouse pointer around in the source window one should accidentally let it touch such an array the debug session is lost.
>How-To-Repeat:
Easy, it fails every time.
>Fix:
In my ignorance, I suspect the problem might be fixed by walking up the call stack and finding the actual dimension of such an array (accounting for the offset if an array element is being passed).
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="test.f"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="test.f"

YyBQcm9ncmFtIHRvIHNob3cgcHJvYmxlbSBpbiBkZGQKICAgICAgaW50ZWdlciBJLCBJQSg1KQog
ICAgICBjYWxsIHN1YjEoSUEpCiAgICAgIHByaW50ICosIChJQShJKSwgSSA9IDEsIDUpCiAgICAg
IHN0b3AKICAgICAgZW5kCiAgICAgIHN1YnJvdXRpbmUgc3ViMShJSSkKICAgICAgaW50ZWdlciBJ
LCBJSSgqKQogICAgICBkbyAxMCBJID0gMSwgNQogICAgICAgIElJKEkpID0gSQogMTAgICBjb250
aW51ZQogICAgICByZXR1cm4KICAgICAgZW5kCgo=