This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2][PR gdb/19893] Fix handling of synthetic C++ references
- From: Pedro Alves <palves at redhat dot com>
- To: Martin Galvan <martin dot galvan at tallertechnologies dot com>
- Cc: gdb-patches <gdb-patches at sourceware dot org>
- Date: Wed, 25 May 2016 19:23:57 +0100
- Subject: Re: [PATCH v2][PR gdb/19893] Fix handling of synthetic C++ references
- Authentication-results: sourceware.org; auth=none
- References: <1464019228-11131-1-git-send-email-martin dot galvan at tallertechnologies dot com> <04d07644-c6ed-88ae-f1de-cba46e875f2d at redhat dot com> <CAOKbPbYGpqAYuV6Vkuq9pGVCh8g=Exwh951K6uXiLc0QCte7eQ at mail dot gmail dot com> <d646b112-1542-ff3d-a018-dbbef37e3eca at redhat dot com> <CAOKbPbZjzy=KnbM1BYK27CQC9hfpko=BBT3E3svn6ACQ6_Nrcg at mail dot gmail dot com>
On 05/24/2016 09:35 PM, Martin Galvan wrote:
> So I think before proceeding we should decide which output is better.
> Perhaps we could show @address whenever possible, and <synthetic
> pointer> for the corner cases?
Yes, I think so. Synthetic pointers are really
an implementation detail, not really something users care about.
> On a related note, it'd be great (for debugging at least!) if unions
> such as this had at least a discriminant of sorts.
It's the value's lval type. :-)
> Right now I don't think so. The existing methods should be enough to
> handle these cases. Speaking of which, are there any plans to rewrite
> this sort of object-oriented code in C++? I'd love to take a shot at
> this in the future.
Certainly, that'd be welcome.
Thanks,
Pedro Alves