Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Chris January <chris.january@allinea.com>
To: "Agovic, Sanimir" <sanimir.agovic@intel.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
	"Boell, Keven"	 <keven.boell@intel.com>,
	"Weinmann, Christoph T"	 <christoph.t.weinmann@intel.com>
Subject: RE: Variable Length Arrays (VLA) proposal
Date: Thu, 04 Jul 2013 10:00:00 -0000	[thread overview]
Message-ID: <1372932018.2796.22.camel@gumtree> (raw)
In-Reply-To: <1372928011.2796.13.camel@gumtree>

On Thu, 2013-07-04 at 09:53 +0100, Chris January wrote:
> On Thu, 2013-07-04 at 08:17 +0000, Agovic, Sanimir wrote:
> > Breakpoint 1, test () at vla.f90:4
> > 4           ALLOCATE(vla (3, 4, 5))
> > $1 = <not allocated>
> > type = integer(kind=4), ALLOCATABLE (0:1,0:1,0:1)
> > 5           ALLOCATE(character(len=2) :: str)
> > $2 = (( ( 0, 0) ( 0, 0) ) ( ( 0, 0) ( 0, 0) ) )
> 
> I have had reports this happens with the Fedora version of gfortran
> 4.7.2 (but not with the Debian version, IIRC) - I will look into it.

GDB 7.2 does not support DWARF 4 (specifically DW_FORM_exprloc in this
case) and that is the cause of this problem.

Chris



  parent reply	other threads:[~2013-07-04 10:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 13:03 Agovic, Sanimir
2013-06-28 15:40 ` Chris January
2013-07-01  1:55   ` Joel Brobecker
2013-07-01  8:01     ` Chris January
2013-07-01 15:32   ` Agovic, Sanimir
2013-07-04  8:18   ` Agovic, Sanimir
2013-07-04  9:13     ` Chris January
2013-07-04 11:49       ` Agovic, Sanimir
2013-07-04 16:55         ` Chris January
2013-07-26 11:44           ` Agovic, Sanimir
     [not found]     ` <1372928011.2796.13.camel@gumtree>
2013-07-04 10:00       ` Chris January [this message]
2013-07-02 13:37 ` Jan Kratochvil
2013-07-02 19:21   ` Jan Kratochvil
2013-07-02 22:22     ` Joel Brobecker
2013-07-04 12:32   ` Keven Boell
2013-08-04 19:33     ` Jan Kratochvil
2013-08-07  5:25       ` Keven Boell
2013-08-04 19:02 ` Jan Kratochvil

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=1372932018.2796.22.camel@gumtree \
    --to=chris.january@allinea.com \
    --cc=christoph.t.weinmann@intel.com \
    --cc=gdb@sourceware.org \
    --cc=keven.boell@intel.com \
    --cc=sanimir.agovic@intel.com \
    /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