public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "schneidermark at myfairpoint dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/9395] cannot access allocatable array in fortran90
Date: Wed, 20 Feb 2013 16:49:00 -0000	[thread overview]
Message-ID: <bug-9395-4717-i9RgbjPVzu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9395-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=9395

Mark Schneider <schneidermark at myfairpoint dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
                 CC|                            |schneidermark at
                   |                            |myfairpoint dot net
            Version|7.4                         |unknown
            Summary|can not acces allocatable   |cannot access allocatable
                   |array in fortran90          |array in fortran90
           Severity|normal                      |critical

--- Comment #11 from Mark Schneider <schneidermark at myfairpoint dot net> 2013-02-20 16:49:11 UTC ---
All IDE's based on gfortran/gdb have this problem, including Code:Blocks,
Simply Frotran, NetBeans and Eclipse. It makes it almost impossible to debug
newer code that depends on allocating arrays. And allocatable arrays in fortran
have been around since fortran 90.

-- 
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.


  parent reply	other threads:[~2013-02-20 16:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9395-4717@http.sourceware.org/bugzilla/>
2011-02-16 16:51 ` [Bug fortran/9395] can not acces " joachim.protze at zih dot tu-dresden.de
2011-02-18  0:02 ` jan.kratochvil at redhat dot com
2011-02-25 13:59 ` joachim.protze at zih dot tu-dresden.de
2011-02-25 18:13 ` jan.kratochvil at redhat dot com
2011-08-06 19:18 ` at_gdb at mathalacarte dot com
2012-02-17 16:57 ` at_gdb at mathalacarte dot com
2012-02-17 17:00 ` at_gdb at mathalacarte dot com
2013-02-20 16:49 ` schneidermark at myfairpoint dot net [this message]
2013-02-20 17:17 ` [Bug fortran/9395] cannot access " at_gdb at mathalacarte dot com
2013-02-20 17:39 ` schneidermark at myfairpoint dot net
2013-02-20 17:42 ` jan.kratochvil at redhat dot com
2013-02-20 17:46 ` schneidermark at myfairpoint dot net
2013-06-11  7:06 ` marcialcz at gmail dot com
2013-10-26  9:12 ` sanimir.agovic at intel dot com
2014-02-16 17:46 ` jackie.rosen at hushmail dot com
2014-05-21  8:41 ` dharenberg at ethz dot ch
2014-05-28 19:41 ` schwab at sourceware dot org
2022-10-21 17:04 ` tromey at sourceware 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-9395-4717-i9RgbjPVzu@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).