1 # Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997 Free Software Foundation, Inc.
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 2 of the License, or
6 # (at your option) any later version.
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.
13 # You should have received a copy of the GNU General Public License
14 # along with this program; if not, write to the Free Software
15 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
17 # Please email any bugs, comments, and/or additions to this file to:
18 # bug-gdb@prep.ai.mit.edu
20 # This file was written by Fred Fish. (fnf@cygnus.com)
29 # are we on a target board
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 gdb_suppress_entire_file "Testcase compile failed, so all tests in this file will automatically fail."
41 # Create and source the file that provides information about the compiler
42 # used to compile the test case.
43 if [get_compiler_info ${binfile}] {
47 # Create a core file named "corefile" rather than just "core", to
48 # avoid problems with sys admin types that like to regularly prune all
49 # files named "core" from the system.
51 # Arbitrarily try setting the core size limit to "unlimited" since
52 # this does not hurt on systems where the command does not work and
53 # allows us to generate a core on systems where it does.
55 # Some systems append "core" to the name of the program; others append
56 # the name of the program to "core".
58 catch "system \"(cd ${objdir}/${subdir}; ulimit -c unlimited; ${binfile}; true) >/dev/null 2>&1\""
59 # remote_exec host "${binfile}"
60 foreach i "${objdir}/${subdir}/core ${objdir}/${subdir}/core.coremaker.c ${binfile}.core" {
61 if [remote_file build exists $i] {
62 remote_exec build "mv $i ${objdir}/${subdir}/corefile"
67 # The braindamaged HPUX shell quits after the ulimit -c above
68 # without executing ${binfile}. So we try again without the
69 # ulimit here if we didn't find a core file above.
70 # Oh, I should mention that any "braindamaged" non-Unix system has
71 # the same problem. I like the cd bit too, it's really neat'n stuff.
72 catch "system \"(cd ${objdir}/${subdir}; ${binfile}; true) >/dev/null 2>&1\""
73 foreach i "${objdir}/${subdir}/core ${objdir}/${subdir}/core.coremaker.c ${binfile}.core" {
74 if [remote_file build exists $i] {
75 remote_exec build "mv $i ${objdir}/${subdir}/corefile"
81 warning "can't generate a core file - core tests suppressed - check ulimit -c"
87 # Test that we can simply startup with a "-core=corefile" command line arg
88 # and recognize that the core file is a valid, usable core file.
89 # To do this, we must shutdown the currently running gdb and restart
90 # with the -core args. We can't use gdb_start because it looks for
91 # the first gdb prompt, and the message we are looking for occurs
92 # before the first prompt. Also, we can't include GDBFLAGS because
93 # if it is empty, this confuses gdb with an empty argument that it
94 # grumbles about (said grumbling currently being ignored in gdb_start).
97 # Another problem is that on some systems (solaris for example), there
98 # is apparently a limit on the length of a fully specified path to
99 # the coremaker executable, at about 80 chars. For this case, consider
100 # it a pass, but note that the program name is bad.
104 send_user "Spawning $GDB -nw $GDBFLAGS -core=$objdir/$subdir/corefile\n"
107 set oldtimeout $timeout
108 set timeout [expr "$timeout + 60"]
109 verbose "Timeout is now $timeout seconds" 2
110 eval "spawn $GDB -nw $GDBFLAGS -core=$objdir/$subdir/corefile"
112 -re "Core was generated by .*coremaker.*\r\n\#0 .*\(\).*\r\n$gdb_prompt $" {
113 pass "args: -core=corefile"
115 -re "Core was generated by .*\r\n\#0 .*\(\).*\r\n$gdb_prompt $" {
116 pass "args: -core=corefile (with bad program name)"
118 -re ".*registers from core file: File in wrong format.* $" {
119 fail "args: -core=corefile (could not read registers from core file)"
121 -re ".*$gdb_prompt $" { fail "args: -core=corefile" }
122 timeout { fail "(timeout) starting with -core" }
127 # Test that startup with both an executable file and -core argument.
128 # See previous comments above, they are still applicable.
134 send_user "Spawning $GDB -nw $GDBFLAGS $binfile -core=$objdir/$subdir/corefile\n"
138 eval "spawn $GDB -nw $GDBFLAGS $binfile -core=$objdir/$subdir/corefile";
140 -re "Core was generated by .*coremaker.*\r\n\#0 .*\(\).*\r\n$gdb_prompt $" {
141 pass "args: execfile -core=corefile"
143 -re "Core was generated by .*\r\n\#0 .*\(\).*\r\n$gdb_prompt $" {
144 pass "args: execfile -core=corefile (with bad program name)"
146 -re ".*registers from core file: File in wrong format.* $" {
147 fail "args: execfile -core=corefile (could not read registers from core file)"
149 -re ".*$gdb_prompt $" { fail "args: execfile -core=corefile" }
150 timeout { fail "(timeout) starting with -core" }
152 set timeout $oldtimeout
153 verbose "Timeout is now $timeout seconds" 2
157 # Now restart normally.
160 gdb_reinitialize_dir $srcdir/$subdir
163 # Test basic corefile recognition via core-file command.
165 send_gdb "core-file $objdir/$subdir/corefile\n"
167 -re "Core was generated by .*coremaker.*\r\n\#0 .*\(\).*\r\n$gdb_prompt $" {
168 pass "core-file command"
170 -re "Core was generated by .*\r\n\#0 .*\(\).*\r\n$gdb_prompt $" {
171 pass "core-file command (with bad program name)"
173 -re ".*registers from core file: File in wrong format.* $" {
174 fail "core-file command (could not read registers from core file)"
176 -re ".*$gdb_prompt $" { fail "core-file command" }
177 timeout { fail "(timeout) core-file command" }
180 # Test correct mapping of corefile sections by printing some variables.
182 gdb_test "print coremaker_data" "\\\$$decimal = 202"
183 gdb_test "print coremaker_bss" "\\\$$decimal = 10"
184 gdb_test "print coremaker_ro" "\\\$$decimal = 201"
186 if {!$gcc_compiled} then { setup_xfail "hppa*-*-hpux*" }
187 gdb_test "print func2::coremaker_local" "\\\$$decimal = {0, 1, 2, 3, 4}"
189 # Somehow we better test the ability to read the registers out of the core
190 # file correctly. I don't think the other tests do this.
192 gdb_test "bt" "abort.*func2.*func1.*main.*" "backtrace in corefile.exp"
194 # Test ability to read mmap'd data
196 gdb_test "x/8bd buf1" ".*:.*0.*1.*2.*3.*4.*5.*6.*7" "accessing original mmap data in core file"
197 setup_xfail "*-*-sunos*" "*-*-ultrix*" "*-*-aix*"
198 send_gdb "x/8bd buf2\n"
200 -re ".*:.*0.*1.*2.*3.*4.*5.*6.*7.*$gdb_prompt $" {
201 pass "accessing mmapped data in core file"
203 -re "0x\[f\]*:.*Cannot access memory at address 0x\[f\]*.*$gdb_prompt $" {
204 fail "accessing mmapped data (mapping failed at runtime)"
206 -re "0x.*:.*Cannot access memory at address 0x.*$gdb_prompt $" {
207 fail "accessing mmapped data (mapping address not found in core file)"
209 -re ".*$gdb_prompt $" {
210 fail "accessing mmapped data (incorrect data found in core file)"
213 fail "accessing mmapped data (timeout)"
217 # test reinit_frame_cache
221 gdb_test "up" "#\[0-9\]* *\[0-9xa-fH'\]* in .* \\(\\)" "up in corefile.exp"
223 gdb_test "core" "No core file now."