]> git.ipfire.org Git - thirdparty/binutils-gdb.git/blob - gdb/testsuite/gdb.base/corefile.exp
This commit was generated by cvs2svn to track changes on a CVS vendor
[thirdparty/binutils-gdb.git] / gdb / testsuite / gdb.base / corefile.exp
1 # Copyright (C) 1992, 1993, 1994, 1995, 1996 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 2 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, write to the Free Software
15 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */
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 perror "Couldn't compile ${srcfile}"
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".
58 set found 0
59 catch "system \"(cd ${objdir}/${subdir}; ulimit -c unlimited; ${binfile}; true) >/dev/null 2>&1\""
60 # remote_exec host "${binfile}"
61 foreach i "${objdir}/${subdir}/core ${objdir}/${subdir}/core.coremaker.c ${binfile}.core" {
62 if [remote_file build exists $i] {
63 remote_exec build "mv $i ${objdir}/${subdir}/corefile"
64 set found 1
65 }
66 }
67 if { $found == 0 } {
68 # The braindamaged HPUX shell quits after the ulimit -c above
69 # without executing ${binfile}. So we try again without the
70 # ulimit here if we didn't find a core file above.
71 # Oh, I should mention that any "braindamaged" non-Unix system has
72 # the same problem. I like the cd bit too, it's really neat'n stuff.
73 catch "system \"(cd ${objdir}/${subdir}; ${binfile}; true) >/dev/null 2>&1\""
74 foreach i "${objdir}/${subdir}/core ${objdir}/${subdir}/core.coremaker.c ${binfile}.core" {
75 if [remote_file build exists $i] {
76 remote_exec build "mv $i ${objdir}/${subdir}/corefile"
77 set found 1
78 }
79 }
80
81 if { $found == 0 } {
82 warning "can't generate a core file - core tests suppressed - check ulimit -c"
83 return 0
84 }
85 }
86
87 #
88 # Test that we can simply startup with a "-core=corefile" command line arg
89 # and recognize that the core file is a valid, usable core file.
90 # To do this, we must shutdown the currently running gdb and restart
91 # with the -core args. We can't use gdb_start because it looks for
92 # the first gdb prompt, and the message we are looking for occurs
93 # before the first prompt. Also, we can't include GDBFLAGS because
94 # if it is empty, this confuses gdb with an empty argument that it
95 # grumbles about (said grumbling currently being ignored in gdb_start).
96 # **FIXME**
97 #
98 # Another problem is that on some systems (solaris for example), there
99 # is apparently a limit on the length of a fully specified path to
100 # the coremaker executable, at about 80 chars. For this case, consider
101 # it a pass, but note that the program name is bad.
102
103 gdb_exit
104 if $verbose>1 then {
105 send_user "Spawning $GDB -nw $GDBFLAGS -core=$objdir/$subdir/corefile\n"
106 }
107
108 set oldtimeout $timeout
109 set timeout [expr "$timeout + 60"]
110 verbose "Timeout is now $timeout seconds" 2
111 eval "spawn $GDB -nw $GDBFLAGS -core=$objdir/$subdir/corefile"
112 expect {
113 -re "Core was generated by .*coremaker.*\r\n\#0 .*\(\).*\r\n$prompt $" {
114 pass "args: -core=corefile"
115 }
116 -re "Core was generated by .*\r\n\#0 .*\(\).*\r\n$prompt $" {
117 pass "args: -core=corefile (with bad program name)"
118 }
119 -re ".*registers from core file: File in wrong format.* $" {
120 fail "args: -core=corefile (could not read registers from core file)"
121 }
122 -re ".*$prompt $" { fail "args: -core=corefile" }
123 timeout { fail "(timeout) starting with -core" }
124 }
125
126
127 #
128 # Test that startup with both an executable file and -core argument.
129 # See previous comments above, they are still applicable.
130 #
131
132 close;
133
134 if $verbose>1 then {
135 send_user "Spawning $GDB -nw $GDBFLAGS $binfile -core=$objdir/$subdir/corefile\n"
136 }
137
138
139 eval "spawn $GDB -nw $GDBFLAGS $binfile -core=$objdir/$subdir/corefile";
140 expect {
141 -re "Core was generated by .*coremaker.*\r\n\#0 .*\(\).*\r\n$prompt $" {
142 pass "args: execfile -core=corefile"
143 }
144 -re "Core was generated by .*\r\n\#0 .*\(\).*\r\n$prompt $" {
145 pass "args: execfile -core=corefile (with bad program name)"
146 }
147 -re ".*registers from core file: File in wrong format.* $" {
148 fail "args: execfile -core=corefile (could not read registers from core file)"
149 }
150 -re ".*$prompt $" { fail "args: execfile -core=corefile" }
151 timeout { fail "(timeout) starting with -core" }
152 }
153 set timeout $oldtimeout
154 verbose "Timeout is now $timeout seconds" 2
155
156 close;
157
158 # Now restart normally.
159
160 gdb_start
161 gdb_reinitialize_dir $srcdir/$subdir
162 gdb_load ${binfile}
163
164 # Test basic corefile recognition via core-file command.
165
166 send_gdb "core-file $objdir/$subdir/corefile\n"
167 expect {
168 -re "Core was generated by .*coremaker.*\r\n\#0 .*\(\).*\r\n$prompt $" {
169 pass "core-file command"
170 }
171 -re "Core was generated by .*\r\n\#0 .*\(\).*\r\n$prompt $" {
172 pass "core-file command (with bad program name)"
173 }
174 -re ".*registers from core file: File in wrong format.* $" {
175 fail "core-file command (could not read registers from core file)"
176 }
177 -re ".*$prompt $" { fail "core-file command" }
178 timeout { fail "(timeout) core-file command" }
179 }
180
181 # Test correct mapping of corefile sections by printing some variables.
182
183 gdb_test "print coremaker_data" "\\\$$decimal = 202"
184 gdb_test "print coremaker_bss" "\\\$$decimal = 10"
185 gdb_test "print coremaker_ro" "\\\$$decimal = 201"
186
187 setup_xfail "i*86-*-sysv4*" "i*86-pc-linux*-gnu" "m68*-*-hpux*"
188 if {!$gcc_compiled} then { setup_xfail "hppa*-*-hpux*" }
189 gdb_test "print func2::coremaker_local" "\\\$$decimal = {0, 1, 2, 3, 4}"
190
191 # Somehow we better test the ability to read the registers out of the core
192 # file correctly. I don't think the other tests do this.
193
194 # Haven't investigated this xfail
195 setup_xfail "m68k-*-hpux*" "i*86-*-sysv4*" "i*86-pc-linux*-gnu"
196 gdb_test "bt" "abort.*func2.*func1.*main.*" "backtrace in corefile.exp"
197
198 # Test ability to read mmap'd data
199
200 gdb_test "x/8bd buf1" ".*:.*0.*1.*2.*3.*4.*5.*6.*7" "accessing original mmap data in core file"
201 setup_xfail "*-*-sunos*" "*-*-ultrix*" "*-*-aix*"
202 send_gdb "x/8bd buf2\n"
203 expect {
204 -re ".*:.*0.*1.*2.*3.*4.*5.*6.*7.*$prompt $" {
205 pass "accessing mmapped data in core file"
206 }
207 -re "0x\[f\]*:.*Cannot access memory at address 0x\[f\]*.*$prompt $" {
208 fail "accessing mmapped data (mapping failed at runtime)"
209 }
210 -re "0x.*:.*Cannot access memory at address 0x.*$prompt $" {
211 fail "accessing mmapped data (mapping address not found in core file)"
212 }
213 -re ".*$prompt $" {
214 fail "accessing mmapped data (incorrect data found in core file)"
215 }
216 timeout {
217 fail "accessing mmapped data (timeout)"
218 }
219 }
220
221 # test reinit_frame_cache
222
223 gdb_load ${binfile}
224 setup_xfail "*-*-*"
225 gdb_test "up" "#\[0-9\]* *\[0-9xa-fH'\]* in .* \\(\\)" "up in corefile.exp"
226
227 gdb_test "core" "No core file now."