gdb/gdbtypes.h: Fix comparison of uninitialized values
authorLancelot SIX <lsix@lancelotsix.com>
Thu, 24 Dec 2020 16:01:21 +0000 (11:01 -0500)
committerSimon Marchi <simon.marchi@polymtl.ca>
Thu, 24 Dec 2020 16:02:55 +0000 (11:02 -0500)
commitf8676776828c6c0c26da31de0de68c0f4162a8e9
treeaf0220f4d16694ca6f0220e3ea33227a92958d34
parent99d8bab0c125618005b96cbca9bae94919ae93b7
gdb/gdbtypes.h: Fix comparison of uninitialized values

When called with an array type of unknown dimensions,
is_scalar_type_recursive ended up comparing uninitialized values.

This was picked up by the following compiler warning:

  CXX    gdbtypes.o
/binutils-gdb/gdb/gdbtypes.c: In function int is_scalar_type_recursive(type*):
/binutils-gdb/gdb/gdbtypes.c:3670:38: warning: high_bound may be used uninitialized in this function [-Wmaybe-uninitialized]
 3670 |       return high_bound == low_bound && is_scalar_type_recursive (elt_type);
      | ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/binutils-gdb/gdb/gdbtypes.c:3670:38: warning: low_bound may be used uninitialized in this function [-Wmaybe-uninitialized]

This patch makes sure that when dealing with an array of unknown size
(or an array of more than 1 element), is_scalar_type_recursive returns
false.

gdb/ChangeLog:

* gdbtypes.c (is_scalar_type_recursive): Prevent comparison
between uninitialized values.

Change-Id: Ifc005ced166aa7a065fef3e652977bae67625bf4
gdb/ChangeLog
gdb/gdbtypes.c
This page took 0.029252 seconds and 4 git commands to generate.