Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Simon Marchi <simon.marchi@polymtl.ca>,
	gdb@sourceware.org
Subject: Re: How to load C++ pretty-printers
Date: Sun, 17 Mar 2019 11:03:00 -0000	[thread overview]
Message-ID: <20190317110310.GA4414@adacore.com> (raw)
In-Reply-To: <ff7a2e36-f3e9-c2c3-5e29-a7d723e6ed1b@gmail.com>

Hello Asmwarrior,

On Sun, Mar 17, 2019 at 09:47:35AM +0800, asmwarrior wrote:
> On Sun Mar 17 2019 00:00:29 GMT+0800, Eli Zaretskii wrote:
> > So, for the record, I now have this in my ~/.gdbinit
> > 
> >   python import sys
> >   python sys.path.insert(0, 'd:/usr/share/gcc-7.3.0/python')
> >   source d:/usr/lib/gcc/mingw32/7.3.0/libstdc++.dll.a-gdb.py
> > 
> > (The last line both imports the function register_libstdcxx_printers,
> > and calls that function.)
> 
> Thanks Eli and Simon.
> 
> I think I have followed this wiki page: https://sourceware.org/gdb/wiki/STLSupport
> And I just the svn command to check-out the latest Python libstdc++
> printers in GCC trunk.  So, that page should be updated, at least we
> can teach people how to use the python printer bundled with their GCC
> release.

It is a fair comment. Would you volunteer to help us update it?

-- 
Joel


  reply	other threads:[~2019-03-17 11:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16  8:30 Eli Zaretskii
2019-03-16 12:41 ` asmwarrior
2019-03-16 12:58   ` Eli Zaretskii
2019-03-16 13:21     ` asmwarrior
2019-03-16 14:25     ` Simon Marchi
2019-03-16 16:00       ` Eli Zaretskii
2019-03-17  1:47         ` asmwarrior
2019-03-17 11:03           ` Joel Brobecker [this message]
2019-03-17 12:39             ` Philippe Waroquiers
2019-03-17 15:31               ` Eli Zaretskii
2019-03-17 17:17                 ` Philippe Waroquiers

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=20190317110310.GA4414@adacore.com \
    --to=brobecker@adacore.com \
    --cc=asmwarrior@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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