From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] embryo of type/main_type pretty_printing...
Date: Wed, 23 Dec 2009 07:08:00 -0000 [thread overview]
Message-ID: <20091223070831.GU2788@adacore.com> (raw)
In-Reply-To: <m3aaxa7sw7.fsf@fleche.redhat.com>
Thanks, Daniel and Tom, for taking the time to review the script!
Once checked in, please feel free to rework/enhance as you see fit.
I'll definitely get to it again, but I really want to look at my
DW_AT_GNAT_descriptive_type patch, which will make the gnat-stuff
thing much simpler. I'm pretty sure the patch is ready, but I want
to have another good read + testing before posting.
> Regardless of whether you decide to change this, I think you should
> check this in. That will make it simpler for us to improve it.
I agree that checking it in would be useful. I just don't know where,
yet. Should we start a "contrib" directory? Or just in the gdb/ directory
itself if we consider this as port of the GDB sources?
I had also had questions about whether we want to enable this script
by default or not. For now, obviously not, since we really have not
finished discussing the output format (not to mention testing). But
this affects, IMO, the location where we want to store the script.
I was thinking about having the "make" install that script in the
build directory besides the gdb exe so that it gets automatically
used. Or perhaps we can use a different strategy of adding the source
path to one of the search paths that GDB uses... WDYT?
--
Joel
next prev parent reply other threads:[~2009-12-23 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-20 7:41 Joel Brobecker
2009-12-22 18:42 ` Tom Tromey
2009-12-23 7:08 ` Joel Brobecker [this message]
2010-01-05 23:12 ` Tom Tromey
2010-01-06 3:51 ` Joel Brobecker
2009-12-22 19:24 ` 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=20091223070831.GU2788@adacore.com \
--to=brobecker@adacore.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