1# Copyright 2003, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, Inc.
2
3# This program is free software; you can redistribute it and/or modify
4# it under the terms of the GNU General Public License as published by
5# the Free Software Foundation; either version 3 of the License, or
6# (at your option) any later version.
7#
8# This program is distributed in the hope that it will be useful,
9# but WITHOUT ANY WARRANTY; without even the implied warranty of
10# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
11# GNU General Public License for more details.
12#
13# You should have received a copy of the GNU General Public License
14# along with this program.  If not, see <http://www.gnu.org/licenses/>.
15
16# Tests for PR gdb/1250.
17# 2003-07-15  Michael Chastain <mec@shout.net>
18
19# This file is part of the gdb testsuite.
20
21if $tracelevel then {
22        strace $tracelevel
23        }
24
25#
26# test running programs
27#
28
29set testfile "gdb1250"
30set srcfile ${testfile}.c
31set binfile ${objdir}/${subdir}/${testfile}
32
33if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
34     untested gdb1250.exp
35     return -1
36}
37
38gdb_exit
39gdb_start
40gdb_reinitialize_dir $srcdir/$subdir
41gdb_load ${binfile}
42
43if ![runto abort {allow-pending}] then {
44    continue
45}
46
47# See http://sources.redhat.com/gdb/bugs/1250
48#
49# In a nutshell: the function 'beta' ends with a call to 'abort', which
50# is a noreturn function.  So the last instruction of 'beta' is a call
51# to 'abort'.  When gdb looks for information about the caller of
52# 'beta', it looks at the instruction after the call to 'abort' -- which
53# is the first instruction of 'alpha'!  So gdb uses the wrong frame
54# information.  It thinks that the test program is in 'alpha' and that
55# the prologue "push %ebp / mov %esp,%ebp" has not been executed yet,
56# and grabs the wrong values.
57#
58# By the nature of the bug, it could pass if the C compiler is not smart
59# enough to implement 'abort' as a noreturn function.  This is okay.
60# The real point is that users often put breakpoints on noreturn
61# functions such as 'abort' or some kind of exitting function, and those
62# breakpoints should work.
63
64gdb_test_multiple "backtrace" "backtrace from abort" {
65    -re "#0.*abort.*\r\n#1.*beta.*\r\n#2.*alpha.*\r\n#3.*main.*\r\n$gdb_prompt $" {
66	pass "backtrace from abort"
67    }
68    -re "#0.*abort.*\r\n#1.*beta.*\r\n$gdb_prompt $" {
69	# This happens with gdb HEAD as of 2003-07-13, with gcc 3.3,
70	# binutils 2.14, either -gdwarf-2 or -gstabs+, on native
71	# i686-pc-linux-gnu.
72	#
73	# gdb gets 'abort' and 'beta' right and then goes into the
74	# weeds.
75	kfail "gdb/1250" "backtrace from abort"
76    }
77}
78