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