This is the mail archive of the
mailing list for the GCC project.
Re: RFA: PATCH to add pp command to gdbinit.in
- From: Marek Polacek <polacek at redhat dot com>
- To: Jason Merrill <jason at redhat dot com>
- Cc: Jeff Law <law at redhat dot com>, gcc-patches List <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 13 Dec 2018 12:52:22 -0500
- Subject: Re: RFA: PATCH to add pp command to gdbinit.in
- References: <CADzB+2mSSYbHJxP=d3KuKZForEHDWnVstx4QOtS-SL2DXqB9FQ@mail.gmail.com> <firstname.lastname@example.org> <20181213172651.GG21364@redhat.com> <CADzB+2nf=6PG2oor6+Hy0MeOhjcjtAcdAzJ68XapOurVgncj-A@mail.gmail.com>
On Thu, Dec 13, 2018 at 12:48:37PM -0500, Jason Merrill wrote:
> On Thu, Dec 13, 2018 at 12:26 PM Marek Polacek <email@example.com> wrote:
> > On Thu, Dec 13, 2018 at 10:15:07AM -0700, Jeff Law wrote:
> > > On 12/6/18 1:59 PM, Jason Merrill wrote:
> > > > Since pvt was removed, it's bugged me that to pretty-print a vec I
> > > > needed to write out "call debug($)". So this patch adds a generic
> > > > command "pp" to print anything handled by a debug overload.
> > > >
> > > > OK for trunk?
> > > >
> > > Seems quite reasonable. I didn't even know we had a debug method for vecs.
> > > I wonder if we should standardize this stuff so that every significant
> > > datastructure has a debug method.
> Yes, I thought that was the idea.
> > Yeah, I think go ahead. Speaking of which, in the C++ FE, I used to could do
> > this:
> > (gdb) call debug(parser)
> > but that now prints some crap like , and so I have to type
> > (gdb) call cp_debug_parser(stderr,parser)
> > which bothers me very very much. Anyone know what's up with that? It used to
> > work.
> Hmm, it works for me.
Aha -- I had to
(gdb) set overload-resolution on
which I had had set to off for some other reasons.