public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "stanton at haas dot berkeley.edu" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18436] New: Can't print dynamically allocated global array
Date: Wed, 20 May 2015 04:54:00 -0000	[thread overview]
Message-ID: <bug-18436-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=18436

            Bug ID: 18436
           Summary: Can't print dynamically allocated global array
           Product: gdb
           Version: 7.9
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: stanton at haas dot berkeley.edu
  Target Milestone: ---

If I dynamically allocate memory for an array using malloc, if the pointer is
defined globally, when I ask gdb to print an element of the array I get the
error message

cannot subscript something of type `<data variable, no debug info>'

Here's a very short program that demonstrates the problem. Compile with 

gcc -g -c -o main.o main.c
gcc -o main main.o 

then, using gdb, step into the middle of the loop and try "print vec[0]". It
works fine if the "double *vec;" line is inside main().

#include <stdio.h>
#include <stdlib.h>

double *vec;

int main(int argc, char *argv[])
{
    int i;

    vec = (double *) malloc((unsigned) 10*sizeof(double));

    for (i=0; i<10; i++) {
        vec[i] = i;
        printf("Item %d = %15.6g\n", i, vec[i]);
    }

    free((char*) vec);

    return(0);
}

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2015-05-20  4:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  4:54 stanton at haas dot berkeley.edu [this message]
2015-05-20 16:34 ` [Bug gdb/18436] " keiths at redhat dot com
2015-05-20 17:15 ` stanton at haas dot berkeley.edu
2015-05-20 17:48 ` keiths at redhat dot com
2015-05-20 18:13 ` stanton at haas dot berkeley.edu
2015-05-21 17:26 ` stanton at haas dot berkeley.edu
2023-08-03 15:53 ` 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-18436-4717@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).