public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] Copy gdb-gdb.py to build dir
Date: Wed, 27 Jun 2018 18:39:00 -0000	[thread overview]
Message-ID: <193ee23e-e72d-9a76-9c1d-865b7afaa527@ericsson.com> (raw)
In-Reply-To: <1529098041-2212-1-git-send-email-simon.marchi@ericsson.com>

On 2018-06-15 05:27 PM, Simon Marchi wrote:
> I have thought for a long time how nice it would be to have cool pretty
> printers for GDB's internal types.  Well, turns out there are few
> already in gdb-gdb.py!  Unfortunately, if you build GDB outside of the
> source directory, that file never gets loaded.  top-gdb will look for a
> file called
> 
>   ../path/to/build/gdb/gdb-gdb.py
> 
> but that file is in the source directory at
> 
>   ../path/to/src/gdb/gdb-gdb.py
> 
> This patch makes it so we copy it to the build directory, just like we
> do for gdb-gdb.gdb.  With this, I can at least see the file getting
> automatically loaded:
> 
> (top-gdb) info pretty-printer
> global pretty-printers:
>   builtin
>     mpx_bound128
>   objfile /home/emaisin/build/binutils-gdb/gdb/gdb pretty-printers:
>   type_lookup_function
> 
> I noticed that running "make" didn't re-generate gdb-gdb.py from
> gdb-gdb.py.in.  That's because it's copied when running the configure
> script and that's it.  I added a rule in the Makefile for that (and for
> gdb-gdb.gdb too) and added them as a dependency to the "all" target.

I pushed these.

Simon

      parent reply	other threads:[~2018-06-27 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 21:27 Simon Marchi
2018-06-15 21:27 ` [PATCH 2/3] gdb-gdb.py.in: Fix ordering of TypeFlags objects with Python 3 Simon Marchi
2018-06-15 21:28 ` [PATCH 3/3] gdb-gdb.py.in: Don't print value's tag_name Simon Marchi
2018-06-27 18:39 ` Simon Marchi [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=193ee23e-e72d-9a76-9c1d-865b7afaa527@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).