Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Daniel Miller (IMI)" <dan@imi-test.com>
Cc: gdb@sources.redhat.com
Subject: Re: cannot subscript something of type <data variable, no debug info>
Date: Sat, 21 Aug 2004 02:11:00 -0000	[thread overview]
Message-ID: <20040821021144.GA3321@nevyn.them.org> (raw)
In-Reply-To: <005601c4871d$67c8c9f0$0401a8c0@dan>

On Fri, Aug 20, 2004 at 06:23:03PM -0700, Daniel Miller (IMI) wrote:
> I'm trying to debug an application with gdb... I have a struct that is
> declared thus:
> 
> typedef struct S_Module_s
> {
>   unsigned powered_up;
>        ...  other data elements  ...
> } __attribute__ ((__packed__)) S_Module;
> 
> extern S_Module Mod[1];
> 
> I tried compiling both with -g and -ggdb, with no change in the symptoms.

What platform?  What version of GDB?

> I don't seem to be able to display any of the contents of Mod[0], at all....
> I get effects such as:
> 
> (gdb) p Mod[0]
> cannot subscript something of type `<data variable, no debug info>'
> (gdb) p (S_Module) Mod[0]
> No symbol "S_Module" in current context.
> (gdb) p (struct S_Module_s) Mod[0]
> No struct type named S_Module_s.
> 
> What do I have to do to get gdb to recognize my variables??  Virtually every
> GUI-based debugger out there is a wrapper around gdb, to if it's not happy,
> nobody's happy!!!  Please help!!

We'll need a standalone test case, or at least a dump of the debugging
information in the application, to answer this question.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-08-21  2:11 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 [this message]
2004-08-23 20:49   ` Daniel Miller (IMI)
2004-08-23 21:15     ` Michael Chastain
2004-08-23 21:28     ` Michael Chastain
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=20040821021144.GA3321@nevyn.them.org \
    --to=drow@false.org \
    --cc=dan@imi-test.com \
    --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