From: Daniel Jacobowitz <drow@false.org>
To: Toby White <tow21@cam.ac.uk>
Cc: gdb@sources.redhat.com
Subject: Re: No symbol "var" in current context
Date: Wed, 26 Jan 2005 15:03:00 -0000 [thread overview]
Message-ID: <20050126150256.GA16939@nevyn.them.org> (raw)
In-Reply-To: <41F7AE4A.3010000@cam.ac.uk>
On Wed, Jan 26, 2005 at 02:50:50PM +0000, Toby White wrote:
> I understand that there is no symbol "var" in current context. However:
> is there a way to ask gdb "well, which symbols are in current context,
> then?"
>
> Background - I'm using gdb with various Fortran compilers which have
> useless debuggers (in this case, NAG, whose own debugger won't even read
> corefiles) and these compilers use weird and wonderful name-mangling
> systems. I suspect in several cases I'm getting the above error messages
> not because the variable has been optimized away, but just because I'm
> not clever enough to work out exactly how it's been name-mangled.
Try "info locals".
--
Daniel Jacobowitz
prev parent reply other threads:[~2005-01-26 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 14:50 Toby White
2005-01-26 15:03 ` Daniel Jacobowitz [this message]
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=20050126150256.GA16939@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=tow21@cam.ac.uk \
/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).