This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v3 1/2] D: Support looking up symbols in the current and imported modules
- From: Iain Buclaw <ibuclaw at gdcproject dot org>
- To: Pierre-Marie de Rodat <derodat at adacore dot com>
- Cc: GDB Patches <gdb-patches at sourceware dot org>, Doug Evans <xdje42 at gmail dot com>
- Date: Tue, 4 Aug 2015 12:48:22 +0200
- Subject: Re: [PATCH v3 1/2] D: Support looking up symbols in the current and imported modules
- Authentication-results: sourceware.org; auth=none
- References: <CABOHX+diCq3hB1g66c7hhoCgfJ9A67EiSBd-E99edrWHskWKbQ at mail dot gmail dot com> <55C07787 dot 9090605 at adacore dot com>
On 4 August 2015 at 10:27, Pierre-Marie de Rodat <derodat@adacore.com> wrote:
> Hello,
>
> On 08/03/2015 08:00 PM, Iain Buclaw wrote:
>>
>> Rebased this against master, in particular to make it compatible with
>> the recent block_symbol additions. I don't have a GCC-4.1 compiler at
>> hand, but I don't think I'm doing anything that may trigger build
>> warnings. Pierre, maybe you want to confirm?
>
>
> Well, I don't have easy access to one neither. ;-) I had a very quick look
> at your patch and it seems that all usage of block_symbol variables are
> dominated by at least one affectation (sym = lookup...), so I guess the
> problem Ulrich and Steve noticed should not arise here.
>
> ... except maybe in one place: in find_symbol_in_baseclass, the returned
> value is uninitialized if we don't enter the FOR loop (is that only possible
> in practice?). So what about providing {NULL, NULL} as an ininialization
> value to "sym", there?
>
> --
> Pierre-Marie de Rodat
Nice catch! Yes, that seems reasonable. I think in the original it
was initialized to NULL...
Regards
Iain.