This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Do not consider reference types as dynamic
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Pierre-Marie de Rodat <derodat at adacore dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, GDB Patches <gdb-patches at sourceware dot org>
- Date: Fri, 17 Apr 2015 11:47:03 +0100
- Subject: Re: [PATCH] Do not consider reference types as dynamic
- Authentication-results: sourceware.org; auth=none
- References: <54FEDC09 dot 3050106 at adacore dot com> <20150323133627 dot GG5438 at adacore dot com> <551BB1C9 dot 10006 at adacore dot com> <551E5309 dot 7090509 at adacore dot com>
Pierre-Marie de Rodat <derodat@adacore.com> writes:
> I've tried to do this and this still triggers no regression on
> x86_64-linux. It's not surprising actually, since
> resolve_dynamic_type_internal does nothing on a type when
> is_dynamic_type_internal returns false for it.
Hi, Pierre,
This patch causes a regression in gdb.cp/vla-cxx.exp unfortunately,
print vlaref^M
$2 = (int (&)[variable length]) @0x3fffffffe900: {5, 7, 9}^M
(gdb) FAIL: gdb.cp/vla-cxx.exp: print vlaref
which is shown by buildbot
https://sourceware.org/ml/gdb-testers/2015-q2/msg00360.html
I am not familiar with gdb type and dynamic type, so can't give anything
useful on how to fix this regression. Any thoughts?
--
Yao (éå)