This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 8/9] class-local typedef substitutions
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 01 Nov 2012 15:01:05 -0600
- Subject: Re: [PATCH 8/9] class-local typedef substitutions
- References: <87vcfphdl8.fsf@fleche.redhat.com> <87sjabrx4g.fsf@fleche.redhat.com> <5091795B.7020506@redhat.com>
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Tom> More testing revealed an oddity in this code (a latent bug exposed by
Tom> the subsequent Python patch); and the fix I chose required some changes
Tom> to some MI test cases as well. The particular change was that
Tom> previously gdb could emit "long int" but now it will emit just "long" --
Tom> I consider this to be an ok (perhaps even preferable) change.
Pedro> I'm confused and curious at why such a change would be necessary. I
Pedro> couldn't find it from a quick look over the patch.
Pedro> Can you expand a little? Does this also affect the CLI?
It has been a while, but I think the difference depends on whether the
type name is sent through canonicalization or not.
Pedro> Why expect both long and "long int"? Is this compiler / debug format
Pedro> dependent, perhaps?
I will take another look and figure it out.
Tom