Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: [rfa/testsuite] test script for pr gdb/1056, divide by zero in gdb
Date: Sat, 18 Oct 2003 15:25:00 -0000	[thread overview]
Message-ID: <200310181525.h9IFPFie019882@duracef.shout.net> (raw)

This is a new test script.  It tests for PR gdb/1056.

  http://sources.redhat.com/gdb/bugs/1056
  divide by 0 hangs gdb

The test script includes some comments which analyze the problem.

The test script accepts any output from gdb followed by $gdb_prompt
as okay.  A timeout results in a KFAIL.

Testing: I ran this script on native i686-pc-linux-gnu, red hat 8.0.
The result was a KFAIL.

Okay to commit?

Michael C

===

2003-10-18  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

# See http://sources.redhat.com/gdb/bugs/1056
#
# 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"
    }
}


             reply	other threads:[~2003-10-18 15:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-18 15:25 Michael Elizabeth Chastain [this message]
2003-10-18 16:41 ` Joel Brobecker
2003-10-18 17:01 Michael Elizabeth Chastain
2003-10-21  0:04 ` Andrew Cagney
2003-10-21  0:32 Michael Elizabeth Chastain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200310181525.h9IFPFie019882@duracef.shout.net \
    --to=mec@shout.net \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox