Files
binutils-gdb/gdb/testsuite/gdb.ada/inline-section-gc.exp
Tom Tromey 6d263fe46e Avoid bad breakpoints with --gc-sections
We found a case where --gc-sections can cause gdb to set an invalid
breakpoint.  In the included test case, gdb will set a breakpoint with
two locations, one of which is 0x0.

The code in lnp_state_machine::check_line_address is intended to
filter out this sort of problem, but in this case, the entire CU is
empty, causing unrelocated_lowpc==0x0 -- which circumvents the check.

It seems to me that if a CU is empty like this, then it is ok to
simply ignore the line table, as there won't be any locations anyway.
2022-01-20 07:22:23 -07:00

42 lines
1.3 KiB
Plaintext

# Copyright 2022 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
load_lib "ada.exp"
if { [skip_ada_tests] } { return -1 }
standard_ada_testfile caller
set options {
debug
optimize=-O2
additional_flags=-ffunction-sections
additional_flags=-largs
additional_flags=-Wl,--gc-sections
additional_flags=-margs
additional_flags=-gnatn
}
if {[gdb_compile_ada "${srcfile}" "${binfile}" executable $options] != ""} {
return -1
}
clean_restart ${testfile}
set bp_location [gdb_get_line_number "BREAK" ${testdir}/callee.adb]
# The bug here was that gdb would set a breakpoint with two locations,
# one of them at 0x0.
gdb_test "break callee.adb:$bp_location" \
"Breakpoint $decimal at $hex: file .*callee.adb, line $bp_location."