gdb/testsuite/gdb.base/gdb1250.exp

   1 # Copyright 2003, 2007-2012 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
  21 #
  22 # test running programs
  23 #
  24
  25 set testfile "gdb1250"
  26 set srcfile ${testfile}.c
  27 set binfile ${objdir}/${subdir}/${testfile}
  28
  29 if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
  30      untested gdb1250.exp
  31      return -1
  32 }
  33
  34 gdb_exit
  35 gdb_start
  36 gdb_reinitialize_dir $srcdir/$subdir
  37 gdb_load ${binfile}
  38
  39 if ![runto abort {allow-pending}] then {
  40     continue
  41 }
  42
  43 # See http://sources.redhat.com/gdb/bugs/1250
  44 #
  45 # In a nutshell: the function 'beta' ends with a call to 'abort', which
  46 # is a noreturn function.  So the last instruction of 'beta' is a call
  47 # to 'abort'.  When gdb looks for information about the caller of
  48 # 'beta', it looks at the instruction after the call to 'abort' -- which
  49 # is the first instruction of 'alpha'!  So gdb uses the wrong frame
  50 # information.  It thinks that the test program is in 'alpha' and that
  51 # the prologue "push %ebp / mov %esp,%ebp" has not been executed yet,
  52 # and grabs the wrong values.
  53 #
  54 # By the nature of the bug, it could pass if the C compiler is not smart
  55 # enough to implement 'abort' as a noreturn function.  This is okay.
  56 # The real point is that users often put breakpoints on noreturn
  57 # functions such as 'abort' or some kind of exitting function, and those
  58 # breakpoints should work.
  59
  60 gdb_test_multiple "backtrace" "backtrace from abort" {
  61     -re "#0.*abort.*\r\n#1.*beta.*\r\n#2.*alpha.*\r\n#3.*main.*\r\n$gdb_prompt $" {
  62         pass "backtrace from abort"
  63     }
  64     -re "#0.*abort.*\r\n#1.*beta.*\r\n$gdb_prompt $" {
  65         # This happens with gdb HEAD as of 2003-07-13, with gcc 3.3,
  66         # binutils 2.14, either -gdwarf-2 or -gstabs+, on native
  67         # i686-pc-linux-gnu.
  68         #
  69         # gdb gets 'abort' and 'beta' right and then goes into the
  70         # weeds.
  71         kfail "gdb/1250" "backtrace from abort"
  72     }
  73 }