From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] embryo of type/main_type pretty_printing...
Date: Tue, 05 Jan 2010 23:12:00 -0000 [thread overview]
Message-ID: <m3pr5o6tb0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091223070831.GU2788@adacore.com> (Joel Brobecker's message of "Wed, 23 Dec 2009 11:08:31 +0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> I agree that checking it in would be useful. I just don't know where,
Joel> yet. Should we start a "contrib" directory? Or just in the gdb/ directory
Joel> itself if we consider this as port of the GDB sources?
Just in the gdb directory is fine by me.
Joel> I had also had questions about whether we want to enable this script
Joel> by default or not. For now, obviously not, since we really have not
Joel> finished discussing the output format (not to mention testing). But
Joel> this affects, IMO, the location where we want to store the script.
Joel> I was thinking about having the "make" install that script in the
Joel> build directory besides the gdb exe so that it gets automatically
Joel> used. Or perhaps we can use a different strategy of adding the source
Joel> path to one of the search paths that GDB uses... WDYT?
In the build tree we can have gdbinit.in refer to this code.
I would probably defer installing it for now, but either way is fine by
me.
Tom
next prev parent reply other threads:[~2010-01-05 23:12 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
2010-01-05 23:12 ` Tom Tromey [this message]
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=m3pr5o6tb0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=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