binutils-gdb/gdb/testsuite/gdb.python/py-breakpoint-create-fail.exp
Andrew Burgess 1d506c26d9 Update copyright year range in header of all files managed by GDB
This commit is the result of the following actions:

  - Running gdb/copyright.py to update all of the copyright headers to
    include 2024,

  - Manually updating a few files the copyright.py script told me to
    update, these files had copyright headers embedded within the
    file,

  - Regenerating gdbsupport/Makefile.in to refresh it's copyright
    date,

  - Using grep to find other files that still mentioned 2023.  If
    these files were updated last year from 2022 to 2023 then I've
    updated them this year to 2024.

I'm sure I've probably missed some dates.  Feel free to fix them up as
you spot them.
2024-01-12 15:49:57 +00:00

55 lines
1.8 KiB
Plaintext

# Copyright (C) 2016-2024 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/>.
# This file is part of the GDB testsuite. It tests proper handling for
# breakpoint creation failure.
load_lib gdb-python.exp
require allow_python_tests
standard_testfile
if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile}] } {
return -1
}
clean_restart "${testfile}"
if ![runto_main] {
return
}
# The following will create a breakpoint Python wrapper whose construction will
# abort: the requested symbol is not defined. GDB should not keep a reference
# to the wrapper; however it used to...
gdb_test "source py-breakpoint-create-fail.py"
# ... and when it did, as a result, the following breakpoint creation (not
# initiated by the Python API) would dereference the already-freed Python
# breakpoint wrapper, resulting in undefined behavior, sometimes observed as a
# gdb crash, and other times causing the next stop to invoke the Python wrapper
# "stop" method for the object that is not supposed to exist.
gdb_test "break foo"
set test "continuing to foo"
gdb_test_multiple "continue" "$test" {
-re "MyBP\.stop was invoked\!.*$gdb_prompt $" {
fail "$test"
}
-re "Continuing.*Breakpoint 2, foo.*$gdb_prompt $" {
pass "$test"
}
}