gdb/testsuite/gdb.base/corefile.exp

   1 # Copyright 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2007, 2008
   2 # Free Software Foundation, Inc.
   3
   4 # This program is free software; you can redistribute it and/or modify
   5 # it under the terms of the GNU General Public License as published by
   6 # the Free Software Foundation; either version 3 of the License, or
   7 # (at your option) any later version.
   8 #
   9 # This program is distributed in the hope that it will be useful,
  10 # but WITHOUT ANY WARRANTY; without even the implied warranty of
  11 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  12 # GNU General Public License for more details.
  13 #
  14 # You should have received a copy of the GNU General Public License
  15 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
  16
  17 # Please email any bugs, comments, and/or additions to this file to:
  18 # bug-gdb@prep.ai.mit.edu
  19
  20 # This file was written by Fred Fish. (fnf@cygnus.com)
  21
  22 if $tracelevel then {
  23         strace $tracelevel
  24 }
  25
  26 set prms_id 0
  27 set bug_id 0
  28
  29 # are we on a target board
  30 if ![isnative] then {
  31     return
  32 }
  33
  34 set testfile "coremaker"
  35 set srcfile ${testfile}.c
  36 set binfile ${objdir}/${subdir}/${testfile}
  37 if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
  38      untested corefile.exp
  39      return -1
  40 }
  41
  42 # Create and source the file that provides information about the compiler
  43 # used to compile the test case.
  44 if [get_compiler_info ${binfile}] {
  45     return -1;
  46 }
  47
  48 # Create a core file named "corefile" rather than just "core", to
  49 # avoid problems with sys admin types that like to regularly prune all
  50 # files named "core" from the system.
  51 #
  52 # Arbitrarily try setting the core size limit to "unlimited" since
  53 # this does not hurt on systems where the command does not work and
  54 # allows us to generate a core on systems where it does.
  55 #
  56 # Some systems append "core" to the name of the program; others append
  57 # the name of the program to "core"; still others (like Linux, as of
  58 # May 2003) create cores named "core.PID".  In the latter case, we
  59 # could have many core files lying around, and it may be difficult to
  60 # tell which one is ours, so let's run the program in a subdirectory.
  61 set found 0
  62 set coredir "${objdir}/${subdir}/coredir.[getpid]"
  63 file mkdir $coredir
  64 catch "system \"(cd ${coredir}; ulimit -c unlimited; ${binfile}; true) >/dev/null 2>&1\""
  65 #      remote_exec host "${binfile}"
  66 foreach i "${coredir}/core ${coredir}/core.coremaker.c ${binfile}.core" {
  67     if [remote_file build exists $i] {
  68         remote_exec build "mv $i ${objdir}/${subdir}/corefile"
  69         set found 1
  70     }
  71 }
  72 # Check for "core.PID".
  73 if { $found == 0 } {
  74     set names [glob -nocomplain -directory $coredir core.*]
  75     if {[llength $names] == 1} {
  76         set corefile [file join $coredir [lindex $names 0]]
  77         remote_exec build "mv $corefile ${objdir}/${subdir}/corefile"
  78         set found 1
  79     }
  80 }
  81 if { $found == 0 } {
  82     # The braindamaged HPUX shell quits after the ulimit -c above
  83     # without executing ${binfile}.  So we try again without the
  84     # ulimit here if we didn't find a core file above.
  85     # Oh, I should mention that any "braindamaged" non-Unix system has
  86     # the same problem. I like the cd bit too, it's really neat'n stuff.
  87     catch "system \"(cd ${objdir}/${subdir}; ${binfile}; true) >/dev/null 2>&1\""
  88     foreach i "${objdir}/${subdir}/core ${objdir}/${subdir}/core.coremaker.c ${binfile}.core" {
  89         if [remote_file build exists $i] {
  90             remote_exec build "mv $i ${objdir}/${subdir}/corefile"
  91             set found 1
  92         }
  93     }
  94 }
  95
  96 # Try to clean up after ourselves.
  97 remote_file build delete [file join $coredir coremmap.data]
  98 remote_exec build "rmdir $coredir"
  99
 100 if { $found == 0  } {
 101     warning "can't generate a core file - core tests suppressed - check ulimit -c"
 102     return 0
 103 }
 104
 105 #
 106 # Test that we can simply startup with a "-core=corefile" command line arg
 107 # and recognize that the core file is a valid, usable core file.
 108 # To do this, we must shutdown the currently running gdb and restart
 109 # with the -core args.  We can't use gdb_start because it looks for
 110 # the first gdb prompt, and the message we are looking for occurs
 111 # before the first prompt.  Also, we can't include GDBFLAGS because
 112 # if it is empty, this confuses gdb with an empty argument that it
 113 # grumbles about (said grumbling currently being ignored in gdb_start).
 114 # **FIXME**
 115 #
 116 # Another problem is that on some systems (solaris for example), there
 117 # is apparently a limit on the length of a fully specified path to
 118 # the coremaker executable, at about 80 chars.  For this case, consider
 119 # it a pass, but note that the program name is bad.
 120
 121 gdb_exit
 122 if $verbose>1 then {
 123     send_user "Spawning $GDB -nw $GDBFLAGS -core=$objdir/$subdir/corefile\n"
 124 }
 125
 126 set oldtimeout $timeout
 127 set timeout [expr "$timeout + 60"]
 128 verbose "Timeout is now $timeout seconds" 2
 129 eval "spawn $GDB -nw $GDBFLAGS -core=$objdir/$subdir/corefile"
 130 expect {
 131     -re "Couldn't find .* registers in core file.*$gdb_prompt $" {
 132         fail "args: -core=corefile (couldn't find regs)"
 133     }
 134     -re "Core was generated by .*coremaker.*\r\n\#0  .*\(\).*\r\n$gdb_prompt $" {
 135         pass "args: -core=corefile"
 136     }
 137     -re "Core was generated by .*\r\n\#0  .*\(\).*\r\n$gdb_prompt $" {
 138         pass "args: -core=corefile (with bad program name)"
 139     }
 140     -re ".*registers from core file: File in wrong format.* $" {
 141         fail "args: -core=corefile (could not read registers from core file)"
 142     }
 143     -re ".*$gdb_prompt $"       { fail "args: -core=corefile" }
 144     timeout             { fail "(timeout) starting with -core" }
 145 }
 146
 147
 148 #
 149 # Test that startup with both an executable file and -core argument.
 150 # See previous comments above, they are still applicable.
 151 #
 152
 153 close;
 154
 155 if $verbose>1 then {
 156     send_user "Spawning $GDB -nw $GDBFLAGS $binfile -core=$objdir/$subdir/corefile\n"
 157 }
 158
 159
 160 eval "spawn $GDB -nw $GDBFLAGS $binfile -core=$objdir/$subdir/corefile";
 161 expect {
 162     -re "Core was generated by .*coremaker.*\r\n\#0  .*\(\).*\r\n$gdb_prompt $" {
 163         pass "args: execfile -core=corefile"
 164     }
 165     -re "Core was generated by .*\r\n\#0  .*\(\).*\r\n$gdb_prompt $"     {
 166         pass "args: execfile -core=corefile (with bad program name)"
 167     }
 168     -re ".*registers from core file: File in wrong format.* $" {
 169         fail "args: execfile -core=corefile (could not read registers from core file)"
 170     }
 171     -re ".*$gdb_prompt $"       { fail "args: execfile -core=corefile" }
 172     timeout             { fail "(timeout) starting with -core" }
 173 }
 174 set timeout $oldtimeout
 175 verbose "Timeout is now $timeout seconds" 2
 176
 177 close;
 178
 179 # Now restart normally.
 180
 181 gdb_start
 182 gdb_reinitialize_dir $srcdir/$subdir
 183 gdb_load ${binfile}
 184
 185 # Test basic corefile recognition via core-file command.
 186
 187 send_gdb "core-file $objdir/$subdir/corefile\n"
 188 gdb_expect {
 189     -re ".* program is being debugged already.*y or n. $" {
 190         # gdb_load may connect us to a gdbserver.
 191         send_gdb "y\n"
 192         exp_continue;
 193     }
 194     -re "Core was generated by .*coremaker.*\r\n\#0  .*\(\).*\r\n$gdb_prompt $" {
 195         pass "core-file command"
 196     }
 197     -re "Core was generated by .*\r\n\#0  .*\(\).*\r\n$gdb_prompt $" {
 198         pass "core-file command (with bad program name)"
 199     }
 200     -re ".*registers from core file: File in wrong format.* $" {
 201         fail "core-file command (could not read registers from core file)"
 202     }
 203     -re ".*$gdb_prompt $"       { fail "core-file command" }
 204     timeout             { fail "(timeout) core-file command" }
 205 }
 206
 207 # Test correct mapping of corefile sections by printing some variables.
 208
 209 gdb_test "print coremaker_data" "\\\$$decimal = 202"
 210 gdb_test "print coremaker_bss" "\\\$$decimal = 10"
 211 gdb_test "print coremaker_ro" "\\\$$decimal = 201"
 212
 213 gdb_test "print func2::coremaker_local" "\\\$$decimal = \\{0, 1, 2, 3, 4\\}"
 214
 215 # Somehow we better test the ability to read the registers out of the core
 216 # file correctly.  I don't think the other tests do this.
 217
 218 gdb_test "bt" "abort.*func2.*func1.*main.*" "backtrace in corefile.exp"
 219 gdb_test "up" "#\[0-9\]* *\[0-9xa-fH'\]* in .* \\(.*\\).*" "up in corefile.exp"
 220
 221 # Test ability to read mmap'd data
 222
 223 gdb_test "x/8bd buf1" ".*:.*0.*1.*2.*3.*4.*5.*6.*7" "accessing original mmap data in core file"
 224 setup_xfail "*-*-sunos*" "*-*-ultrix*" "*-*-aix*"
 225 set test "accessing mmapped data in core file"
 226 gdb_test_multiple "x/8bd buf2" "$test" {
 227     -re ".*:.*0.*1.*2.*3.*4.*5.*6.*7.*$gdb_prompt $" {
 228         pass "$test"
 229     }
 230     -re "0x\[f\]*:.*Cannot access memory at address 0x\[f\]*.*$gdb_prompt $" {
 231         fail "$test (mapping failed at runtime)"
 232     }
 233     -re "0x.*:.*Cannot access memory at address 0x.*$gdb_prompt $" {
 234         fail "$test (mapping address not found in core file)"
 235     }
 236 }
 237
 238 # test reinit_frame_cache
 239
 240 gdb_load ${binfile}
 241 gdb_test "up" "#\[0-9\]* *\[0-9xa-fH'\]* in .* \\(.*\\).*" "up in corefile.exp (reinit)"
 242
 243 gdb_test "core" "No core file now."