public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/9395] can not acces allocatable array in fortran90
Date: Fri, 25 Feb 2011 18:13:00 -0000	[thread overview]
Message-ID: <bug-9395-4717-SjPuyX12yL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9395-4717@http.sourceware.org/bugzilla/>

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

--- Comment #8 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2011-02-25 18:13:48 UTC ---
(In reply to comment #7)
> It seems, that we now have infinite loops in some cases

Thanks, the code was reading some memory after the end of the array.

For small arrays it makes no difference but with such a large array GDB tried
to read unmapped memory pages which resulted in very ptrace reading and day it
would say:
Cannot access memory at address 0x7ffff0c75f58

Fixed now on archer-jankratochvil-vla by:
530ce8bb0aeeb513f566da7a7fae46d6414f8dc1

(gdb) p buffer(10,10,9:10)
$1 = (813010, 903010)

The VLA code needs a rewrite for merge, though.  I do not find viable to fix
the Comment 4 with the current codebase.

-- 
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:[~2011-02-25 18:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9395-4717@http.sourceware.org/bugzilla/>
2011-02-16 16:51 ` 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 [this message]
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 ` [Bug fortran/9395] cannot access " schneidermark at myfairpoint dot net
2013-02-20 17:17 ` 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
     [not found] <20070726092801.9395.virginie.trinite@thalesgroup.com>
2008-12-23 19:43 ` [Bug fortran/9395] can not acces " jan dot kratochvil at redhat dot com
2009-07-15  9:00 ` mhp77 at gmx dot at
2009-10-02 13:23 ` jan dot kratochvil at redhat dot com
2010-01-11 13:10 ` mhp77 at gmx dot at
2010-01-12 15:21 ` mhp77 at gmx dot at
2010-06-29 15:11 ` jan dot kratochvil at redhat 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-9395-4717-SjPuyX12yL@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).