public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: potterveld@anl.gov
To: gcc-gnats@gcc.gnu.org
Subject: debug/10561: g77/gdb incorrectly maps variables in fortran common block
Date: Wed, 30 Apr 2003 05:16:00 -0000	[thread overview]
Message-ID: <20030430051424.32317.qmail@sources.redhat.com> (raw)


>Number:         10561
>Category:       debug
>Synopsis:       g77/gdb incorrectly maps variables in fortran common block
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 30 05:16:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     David Potterveld
>Release:        gcc: 3.2,3, gdb: 5.3
>Organization:
>Environment:
HP/Compaq/Dec Alpha, Tru64 unix 4.0f (aka OSF/1)
>Description:
gdb can't print variables in common. It appears to try reading  a low memory address related to the variable offset in the common, ie, the offset to the start of the common is neglected.
Sample program:
      program xxx
      common /x/ a,b
      a = 47
      b = 2
      end

compile with "g77 -g -O0 -o xxx xxx.f"
debug with: "gdb xxx"
gdb commands: [ Output:]
------------------------------------------------------
break MAIN__ 
run
step
step
print a   [Error accessing memory address 0x8: Invalid argument.]
print &a  [$1 = (PTR TO -> ( real*4 )) 0x8]
print &x_ [$2 = (PTR TO -> ( char (0:7))) 0x1400001d0]
print (real) x_ [$3 = 47]

Clearly, gdb is aware of variable "a", but has the wrong address for it.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-04-30  5:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030430051424.32317.qmail@sources.redhat.com \
    --to=potterveld@anl.gov \
    --cc=gcc-gnats@gcc.gnu.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).