This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [4/5] implement "info vtable"
- From: Pedro Alves <palves at redhat dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Pedro Alves <palves at redhat dot com>, gdb-patches at sourceware dot org
- Date: Thu, 01 Mar 2012 17:48:28 +0000
- Subject: Re: [4/5] implement "info vtable"
- References: <87mx82prmd.fsf@fleche.redhat.com> <4F4F8D39.60507@redhat.com> <878vjkjka1.fsf@fleche.redhat.com>
On 03/01/2012 05:36 PM, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>
> Pedro> My only gripe is that we end up with the vtable vs vtbl inconsistency
> Pedro> (set print vtbl).
>
> Yeah. I was thinking of renaming 'set print vtbl' (keeping the old name
> as an alias of course). WDYT? I think "vtable" is both clearer and
> more commonly used.
I have no problem with vtbl, but if you think vtable is clearer, fine with me.
> Pedro> May be a good idea if the docs are augmented a bit to give an example,
> Pedro> and lightly explain the output.
>
> Ok.
>
> Pedro> IIUC, "info vtable POINTER" works. The tests only sees to try
> Pedro> "info vtable OBJ". Worth adding a test that tries through a pointer?
>
> Will do.
Thanks. While at it, it might be worth it to add a test that
tries "info vtable" (no arg), "info vtable foo" with a foo object that doesn't
have a vtable, and perhaps also "info vtable some_scalar".
--
Pedro Alves