From: Jerome Guitton <guitton@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA/testsuite] stack check
Date: Mon, 01 Sep 2008 17:03:00 -0000 [thread overview]
Message-ID: <20080901170203.GB226@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
Test that GDB is able to get a correct backtrace when the application
is compiled with -fstack-check. Related to:
http://sourceware.org/ml/gdb-patches/2008-09/msg00005.html
2008-09-01 Jerome Guitton <guitton@adacore.com>
* (stack-checking.c, stack-checking.exp): New testcase.
OK to apply?
Thanks,
- Jerome
[-- Attachment #2: stack-checking.c --]
[-- Type: text/x-csrc, Size: 389 bytes --]
/*
Test file to be compiled with -fstack-check, for testing "bt" against
different stack checking prologue sequences.
*/
int i = 0;
void
small_frame ()
{
i++; /* set breakpoint here */
}
void medium_frame ()
{
char S [16384];
small_frame ();
}
void big_frame ()
{
char S [524188];
small_frame ();
}
void
main ()
{
small_frame ();
medium_frame ();
big_frame ();
}
[-- Attachment #3: stack-checking.exp --]
[-- Type: text/plain, Size: 1665 bytes --]
# Copyright 2008 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/>.
if $tracelevel then {
strace $tracelevel
}
set prms_id 0
set bug_id 0
set testfile "stack-checking"
set srcfile ${testfile}.c
set binfile ${objdir}/${subdir}/${testfile}
if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable [concat debug optimize=-fstack-check nowarnings]] != "" } {
untested stack-checking.exp
return -1
}
gdb_exit
gdb_start
gdb_reinitialize_dir $srcdir/$subdir
gdb_load ${binfile}
if ![runto_main] then {
fail "Can't run to main"
return 0
}
# Test that the debugger is able to unwind to "main" at the next breakpoint
# hit. The frame number of "main" should be passed into MAIN_FRAME_NUMBER."
proc backtrace_test {name main_frame_number} {
gdb_continue_to_breakpoint "breakpoint for $name"
gdb_test "bt" "#${main_frame_number}.*in main ().*"
}
gdb_breakpoint [gdb_get_line_number "set breakpoint here"]
backtrace_test "small frame" "1"
backtrace_test "medium frame" "2"
backtrace_test "big frame" "2"
next reply other threads:[~2008-09-01 17:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 17:03 Jerome Guitton [this message]
2008-09-01 17:14 ` Jerome Guitton
2008-09-02 21:03 ` Joel Brobecker
2008-09-02 21:02 ` Joel Brobecker
2008-09-03 8:53 ` Jerome Guitton
2008-09-08 10:17 ` Jerome Guitton
2008-09-08 15:42 ` Joel Brobecker
2008-09-08 15:56 ` Jerome Guitton
2008-09-11 16:26 ` [commit] Fix testcase for SPU (Re: [RFA/testsuite] stack check) Ulrich Weigand
2008-09-11 16:35 ` Jerome Guitton
2008-09-11 18:12 ` Ulrich Weigand
2008-09-05 10:53 [RFA/testsuite] stack check Jerome Guitton
2008-09-06 2:03 ` Joel Brobecker
2008-09-08 16:05 ` Jerome Guitton
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=20080901170203.GB226@adacore.com \
--to=guitton@adacore.com \
--cc=gdb-patches@sourceware.org \
/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