This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [commit/Ada] Use our builtin type when evaluating conditional expressions
- From: Tom Tromey <tromey at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 17 Mar 2009 14:06:25 -0600
- Subject: Re: [commit/Ada] Use our builtin type when evaluating conditional expressions
- References: <20090313012134.GA11284@adacore.com>
- Reply-to: tromey at redhat dot com
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> (gdb) p null /= null
Jerome> The problem comes from the fact that GDB casts "null /= null"
Jerome> into the language boolean type (i.e. "standard.boolean"). And
Jerome> it lookups the boolean type into the debug info of the
Jerome> application. As type boolean is defined in every compilation
Jerome> unit, every psymtabs matchs; as a consequence, all the
Jerome> corresponding symtabs are built. This roughly means that the
Jerome> debugger loads every symbols when evaluating a conditional
Jerome> expression.
I'm curious whether this will be a problem for any language defining
bool_type_symbol. If so, perhaps a language-neutral fix could be
found. If not, what is it that makes this specific to Ada?
Tom