Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Gdb-Patches@Sources.Redhat.Com" <gdb-patches@sources.redhat.com>
Subject: [patch] New testcase for PR:1291
Date: Fri, 24 Oct 2003 15:40:00 -0000	[thread overview]
Message-ID: <083101c39a45$57631cc0$0202040a@catdog> (raw)

Changelog:

2003-10-24  Kris Warkentin  <kewarken@qnx.com>

 * gdb.arch/gdb1291.c: New test file.
 * gdb.arch/gdb1291.exp: New test script.

-------gdb1291.c--------
sub1()
{
        int buf[64];
}

sub2()
{
        int buf[65];
}

main()
{
        sub1();
        sub2();
}

-----gdb1291.exp-----

# 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.

# Please email any bugs, comments, and/or additions to this file to:
# bug-gdb@gnu.org

# This file is part of the gdb testsuite.

# Tests for PR:1291.  Ensure that backtrace works properly for stack
# frames greater than 256 bytes.

if $tracelevel {
    strace $tracelevel
}

# Test SH backtraces with >256 byte frame stack. (PR:1291)

set prms_id 0
set bug_id 0

if ![istarget "sh-*-*"] then {
    verbose "Skipping SH backtrace tests."
    return
}

set testfile "gdb1291"
set srcfile ${testfile}.c
set binfile ${objdir}/${subdir}/${testfile}
if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable
{debug}] != "" } {
    gdb_suppress_entire_file "Testcase compile failed, so all tests in this
file will automatically fail."
}

gdb_exit
gdb_start
gdb_reinitialize_dir $srcdir/$subdir
gdb_load ${binfile}

#
# Run to `main' where we begin our tests.
#

if ![runto_main] then {
    gdb_suppress_tests
}

gdb_test "u sub1" "sub1*" "get to sub1"
gdb_test "bt" "#0\[ \t\]*sub1 \\(\\) at sh-bt.*\r\n#1\[ \t\]*$hex in main.*"
\
 "backtrace in gdb1291"

gdb_test "u sub2" "sub2*" "get to sub2"
gdb_test "bt" "#0\[ \t\]*sub2 \\(\\) at sh-bt.*\r\n#1\[ \t\]*$hex in main.*"
\
 "backtrace in gdb1291"



             reply	other threads:[~2003-10-24 15:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24 15:40 Kris Warkentin [this message]
2003-10-24 15:59 ` Daniel Jacobowitz
2003-10-24 17:46   ` Kris Warkentin
2003-10-24 17:59     ` Daniel Jacobowitz
2003-10-24 16:01 ` Elena Zannoni
2003-10-24 19:20 Michael Elizabeth Chastain
2003-10-24 19:23 Michael Elizabeth Chastain
2003-10-27 19:01 ` Kris Warkentin
2003-10-28 16:02   ` Elena Zannoni
2003-10-28 16:46     ` Kris Warkentin
2003-10-28 16:49       ` Daniel Jacobowitz

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='083101c39a45$57631cc0$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --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