Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Konstantin Karganov <kostik@ispras.ru>
To: JS <fedevaps@yahoo.dk>
Cc: gdb@sources.redhat.com
Subject: Re: Still cannot print variable
Date: Fri, 15 Apr 2005 09:20:00 -0000	[thread overview]
Message-ID: <238614216.20050415132437@ispras.ru> (raw)
In-Reply-To: <d3o02u$t10$1@sea.gmane.org>

Hello JS,

> I run "gdb test" followed by "print d" and then I get this error:

> No symbol "d" in current context.

> Why is it not possible to see the contents of "d" when debugging?

Because you are not yet debugging!
As described above, you started the debugger but not started the
program being debugged.
Try this:
 gdb test
 break main            // to stop your program run
 run
 print d

-- 
Best regards,
 Konstantin 




  reply	other threads:[~2005-04-15  9:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15  9:09 JS
2005-04-15  9:20 ` Konstantin Karganov [this message]
2005-04-15 10:02   ` JS
2005-04-15 10:11     ` Re[2]: " Konstantin Karganov
2005-04-15 10:22       ` JS
2005-04-15  9:27 ` Joakim Hove
2005-04-15  9:30 ` Eli Zaretskii
2005-04-15 11:55 ` Bob Rossi
2005-04-15 12:01   ` Dave Korn
2005-04-15 12:06   ` Daniel Jacobowitz

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=238614216.20050415132437@ispras.ru \
    --to=kostik@ispras.ru \
    --cc=fedevaps@yahoo.dk \
    --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