forked from Imagelibrary/binutils-gdb
1d506c26d9
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.
44 lines
1.5 KiB
Plaintext
44 lines
1.5 KiB
Plaintext
# Copyright 2003-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/>.
|
|
|
|
# Test for PR gdb/1056.
|
|
# 2003-10-18 Michael Chastain <mec@shout.net>
|
|
|
|
# test SIGFPE (such as division by 0) inside gdb itself
|
|
|
|
|
|
gdb_start
|
|
|
|
# When SIGFPE happens, the operating system may restart the
|
|
# offending instruction after the signal handler returns,
|
|
# rather than proceeding to the next instruction. This happens
|
|
# on i686-pc-linux-gnu with a linux kernel. If gdb has a naive
|
|
# signal handler that just returns, then it will restart the
|
|
# broken instruction and gdb gets an endless stream of SIGFPE's
|
|
# and makes no progress.
|
|
#
|
|
# On a broken gdb this test will just time out.
|
|
|
|
gdb_test_multiple "print 1/0" "" {
|
|
-re ".*$gdb_prompt $" {
|
|
pass "print 1/0"
|
|
}
|
|
timeout {
|
|
kfail "gdb/1056" "print 1/0"
|
|
}
|
|
}
|
|
gdb_test "print 1U/0" ".*Division by zero.*" "test unsigned division by zero"
|
|
|