Re: [rfa/testsuite] test script for pr gdb/1056, divide by zero in gdb

Michael Elizabeth Chastain
2003-10-21T00:32:59Z

ac> While ".../gdb/bugs/<PR>" will out last any switch to mozilla (re-number
ac> over my dead body :-), I don't think people will appreciate having
ac> "redhat" embedded in the file.
ac>
ac> I'd just stick to quoting the GDB pr number and any relevant text.

Err, okay. I wish that I could say "http://gdb.gnu.org/bugs/1234".
But I can't. So I'll delete this line.

# See http://sources.redhat.com/gdb/bugs/1056

Modified patch below. There are still plenty of places that tie it
to gdb pr/1056.

ac> Anyway, yes ok.

I'll take that as approval for the modified patch. Wheee!

I'm committing this now.

Michael C

===

2003-10-20 Michael Chastain <mec@shout.net>

* gdb.base/gdb1056.exp: New test script.

# Copyright 2003 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 2 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, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

# Test for PR gdb/1056.
# 2003-10-18 Michael Chastain <mec@shout.net>

if $tracelevel then {
strace $tracelevel
}

# test SIGFPE (such as division by 0) inside gdb itself

set prms_id 0
set bug_id 0

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"
}
}