Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: drow@false.org, dan@imi-test.com
Cc: gdb@sources.redhat.com
Subject: Re: cannot subscript something of type <data variable, no debug info>
Date: Mon, 23 Aug 2004 21:28:00 -0000	[thread overview]
Message-ID: <412A616D.nailD4K28EC6E@mindspring.com> (raw)
In-Reply-To: <008d01c48952$b7e0e7b0$0401a8c0@dan>

Also, I tried a SuSE 9 system with the vendor-supplied gcc and gdb:

  Linux spe186 2.6.5-7.97-bigsmp #1 SMP Fri Jul 2 14:21:59 UTC 2004 i686 i686 i386 GNU/Linux
  gcc version 3.3.3 (SuSE Linux)
  GNU gdb 6.1
  This GDB was configured as "i586-suse-linux"

Your test program worked fine for me:

  [chastain@spe186 dm]$ gdb tester
  GNU gdb 6.1
  Copyright 2004 Free Software Foundation, Inc.
  GDB is free software, covered by the GNU General Public License, and you are
  welcome to change it and/or distribute copies of it under certain conditions.
  Type "show copying" to see the conditions.
  There is absolutely no warranty for GDB.  Type "show warranty" for details.
  This GDB was configured as "i586-suse-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

  (gdb) print Mod[0]
  $1 = {Stat = 0, sys_status = 0, powered_up = 0, compat = 0}
  (gdb) print (S_Module) Mod[0]
  $2 = {Stat = 0, sys_status = 0, powered_up = 0, compat = 0}

Also try this: right after you start gdb, do "break main"
and "run", to get to the main program.  Then print Mod[0] et cetera.
Does that help any?


  parent reply	other threads:[~2004-08-23 21:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-21  1:23 Daniel Miller (IMI)
2004-08-21  2:11 ` Daniel Jacobowitz
2004-08-23 20:49   ` Daniel Miller (IMI)
2004-08-23 21:15     ` Michael Chastain
2004-08-23 21:28     ` Michael Chastain [this message]
2004-08-23 22:30       ` Daniel Miller (IMI)
2004-08-24  2:20         ` Michael Chastain
2004-08-24 12:12         ` Michael Chastain
2004-08-24 16:25           ` Daniel Miller (IMI)
2004-08-24 16:34             ` Daniel Jacobowitz
2004-08-24 16:40               ` Daniel Miller (IMI)
2004-08-24 16:54             ` Michael Chastain
2004-08-24 16:32           ` Daniel Miller (IMI)
2004-08-24 16:54           ` Daniel Miller (IMI)
2004-08-24 16:55             ` Daniel Jacobowitz
2004-08-24 17:20               ` Michael Chastain
2004-08-24 17:48                 ` Daniel Miller (IMI)
2004-08-24 17:52                   ` Daniel Jacobowitz
     [not found]                 ` <00e001c48a01$014b02b0$0401a8c0@dan>
2004-08-24 17:54                   ` Michael Chastain
2004-08-23 20:56 Daniel Miller (IMI)

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=412A616D.nailD4K28EC6E@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=dan@imi-test.com \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.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