Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: How to load C++ pretty-printers
Date: Sat, 16 Mar 2019 12:58:00 -0000	[thread overview]
Message-ID: <83sgvnx9g1.fsf@gnu.org> (raw)
In-Reply-To: <f9779cd9-b2e2-93dd-ff14-12b6e5a9db23@gmail.com> (message from	asmwarrior on Sat, 16 Mar 2019 20:41:13 +0800)

> From: asmwarrior <asmwarrior@gmail.com>
> Date: Sat, 16 Mar 2019 20:41:13 +0800
> 
> Under My Windows 7 system, I'm using such commands(I put them in a my.gdb script file) to load and register the pretty printers.
> I put the libstdcxx folder in the same folder as the my.gdb file.
>  
> 
> set auto-load safe-path $debugdir;$datadir/auto-load
> python
> import sys
> sys.path.insert(0, '')
> from libstdcxx.v6.printers import register_libstdcxx_printers
> # load other pretty printers
> end

Thanks, but I don't think I understand which part(s) of this are
necessary in my case.  E.g., is the "set auto-load" command
needed/relevant?  And what is the my.gdb file, I don't think I have
such a file on my system.  The pretty-printers that came with GCC are
installed where the GCC installation puts them, and I'd prefer not to
change that if possible.

Also, which of the commands you've shown actually loads the
pretty-printers from their file?

Thanks again for your response.


  reply	other threads:[~2019-03-16 12:58 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 [this message]
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
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=83sgvnx9g1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=asmwarrior@gmail.com \
    --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