Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <aristovski@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: cp-name-parser.y
Date: Mon, 03 Mar 2008 18:33:00 -0000	[thread overview]
Message-ID: <47CC447A.4090508@qnx.com> (raw)
In-Reply-To: <20080303172217.GA4469@caradoc.them.org>

Daniel Jacobowitz wrote:
> Sorry, that's not what I meant.  Any symbol is in one particular
> anonymous namespace when we print it out.  So we could print out
> which anonymous namespace it's in.
Oh, ok. Now I see what you meant.
> 
> So the easiest solution may be to ignore "(anonymous namespace)::"
> during symbol lookup.
> 
> A workaround you could try would be to use quoted symbol names.
> Does this work?
> 
> -var-create - * "'(anonymous namespace)::foobar'"
> 
That worked. Thanks.

I will follow up with this, since it looks like there are other issues for the 
IDE. In particular, there seems to be quite a few cases where gdb can not parse 
forms printed by 'ptype'/'whatis'. I see mi equivalent is not implemented yet so 
maybe this should be taken into account then.




  reply	other threads:[~2008-03-03 18:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 18:39 cp-name-parser.y Aleksandar Ristovski
2008-02-29 19:09 ` cp-name-parser.y Daniel Jacobowitz
2008-02-29 19:32   ` cp-name-parser.y Aleksandar Ristovski
2008-02-29 19:49     ` cp-name-parser.y Daniel Jacobowitz
2008-02-29 20:15       ` cp-name-parser.y Aleksandar Ristovski
2008-02-29 21:49         ` cp-name-parser.y Daniel Jacobowitz
2008-03-03 17:02           ` cp-name-parser.y Aleksandar Ristovski
2008-03-03 17:22             ` Daniel Jacobowitz
2008-03-03 18:33               ` Aleksandar Ristovski [this message]
2008-03-03 20:05                 ` cp-name-parser.y 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=47CC447A.4090508@qnx.com \
    --to=aristovski@qnx.com \
    --cc=drow@false.org \
    --cc=gdb@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