public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51967] FAIL: libstdc++-prettyprinters/48362.cc
Date: Mon, 23 Jan 2012 15:59:00 -0000	[thread overview]
Message-ID: <bug-51967-4-eG4UvCpAq3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51967-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51967

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-01-23 15:39:52 UTC ---
do the printers ever work, outside the testsuite?

i.e. if you build this:
#include <tuple>
int main() {
  std::tuple<int, int> t;
  return std::tuple_size<decltype(t)>::value;
}

then debug and run

  break 4
  run
  print t

you should see

$1 = std::tuple containing = {
  [1] = 0,
  [2] = 0
}


does it make any difference if you put this in ~/.gdbinit (with the correct
path to the installed gcc)?

python
 import sys
 sys.path.insert(0, '/path/to/gcc/share/gcc-4.7.0/python')
 from libstdcxx.v6.printers import register_libstdcxx_printers
 register_libstdcxx_printers (None)
end


  parent reply	other threads:[~2012-01-23 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 15:26 [Bug libstdc++/51967] New: " danglin at gcc dot gnu.org
2012-01-23 15:32 ` [Bug libstdc++/51967] " danglin at gcc dot gnu.org
2012-01-23 15:59 ` redi at gcc dot gnu.org [this message]
2012-01-29 17:51 ` dave.anglin at bell dot net
2012-02-02 20:17 ` bkoz at gcc dot gnu.org
2012-02-02 20:41 ` dave.anglin at bell dot net
2012-02-15 20:27 ` bkoz at gcc dot gnu.org
2012-02-16  3:01 ` dave.anglin at bell dot net
2012-02-21 15:31 ` danglin at gcc dot gnu.org

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=bug-51967-4-eG4UvCpAq3@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).