1 # Copyright 1998, 2000, 2001, 2002, 2003, 2004, 2007, 2008, 2009, 2010, 2011
2 # Free Software Foundation, Inc.
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.
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.
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/>.
17 # This file was written by Kendra.
24 # Test debugging assembly level programs.
25 # This file uses asmsrc[12].s for input.
32 set link-flags "-e _start"
35 switch -glob -- [istarget] {
38 # ??? Won't work with ecoff systems like Tru64, but then we also
39 # don't have any other -g flag that creates mdebug output.
40 set asm-flags "-no-mdebug -I${srcdir}/${subdir} -I${objdir}/${subdir}"
41 set debug-flags "-gdwarf-2"
57 set debug-flags "-gdwarf-2"
66 set asm-arch m32r-linux
73 append link-flags "--whole-archive -lgloss --no-whole-archive"
77 set asm-flags "-mshort-double -m68hc11 --no-warn -I${srcdir}/${subdir} -I${objdir}/${subdir}"
78 set debug-flags "-gdwarf-2"
79 # This asm test is specific and uses the linker directly.
80 # We must not use the target board linker script defined for other
81 # tests. Remove it and restore it later on.
82 set board [target_info name]
83 set old_ldscript [board_info $board ldscript]
84 unset_board_info "ldscript"
88 set asm-flags "-mshort-double -m68hc12 --no-warn -I${srcdir}/${subdir} -I${objdir}/${subdir}"
89 set debug-flags "-gdwarf-2"
90 # This asm test is specific and uses the linker directly.
91 # We must not use the target board linker script defined for other
92 # tests. Remove it and restore it later on.
93 set board [target_info name]
94 set old_ldscript [board_info $board ldscript]
95 set_board_info ldscript ""
101 if { [is_lp64_target] } {
102 set asm-arch powerpc64
103 set asm-flags "-a64 -I${srcdir}/${subdir} -I${objdir}/${subdir}"
104 append link-flags " -m elf64ppc"
107 set asm-flags "-a32 -I${srcdir}/${subdir} -I${objdir}/${subdir}"
108 append link-flags " -m elf32ppc"
113 set debug-flags "-gdwarf-2"
120 set asm-flags "-xarch=v9 -I${srcdir}/${subdir} -I${objdir}/${subdir}"
121 set debug-flags "-gdwarf-2"
125 set asm-flags "-I${srcdir}/${subdir} -I${objdir}/${subdir} --no-warn"
126 set debug-flags "-gdwarf-2"
129 set asm-arch xstormy16
130 set debug-flags "-gdwarf-2"
134 set gdb_wrapper_initialized 1
141 set debug-flags "-gdwarf-2"
148 set debug-flags "-gdwarf-2"
152 set debug-flags "-gdwarf-2"
156 set debug-flags "-gdwarf-2"
160 set debug-flags "-gdwarf-2"
164 if { "${asm-arch}" == "" } {
165 untested asm-source.exp
169 # On NetBSD/ELF we need a special NetBSD-identifying note section.
170 if { [istarget "*-*-netbsdelf*"]
171 || [istarget "alpha-*-netbsd*"]
172 || [istarget "mips*-*-netbsd*"]
173 || [istarget "powerpc-*-netbsd*"]
174 || [istarget "x86_64-*-netbsd*"] } then {
175 set asm-note "netbsd"
178 # On OpenBSD/ELF we need a similar note section. We make no attempt
179 # of handing a.out here since most OpenBSD/a.out systems use a rather
180 # outdated assembler that doesn't assemble this test's code anyway.
181 if { [istarget "*-*-openbsd*"] } then {
182 set asm-note "openbsd"
185 # Watch out, we are invoking the assembler, but the testsuite sets multilib
186 # switches according to compiler syntax. If we pass these options straight
187 # to the assembler, they won't always make sense. If we don't pass them to
188 # the assembler, the final link will complain that the object files were
189 # built with different defaults. So no matter what we do, we lose. We may as
190 # well get out of this test sooner rather than later.
191 set dest [target_info name]
192 if [board_info $dest exists multilib_flags] {
193 set multilib_flags [board_info $dest multilib_flags]
194 if { "${multilib_flags}" != "" } {
195 untested asm-source.exp
201 set testfile "asm-source"
202 set binfile ${objdir}/${subdir}/${testfile}
203 set srcfile1 asmsrc1.s
204 set srcfile2 asmsrc2.s
206 remote_exec build "rm -f ${subdir}/arch.inc"
207 remote_download host ${srcdir}/${subdir}/${asm-arch}.inc ${subdir}/arch.inc
208 remote_exec build "rm -f ${subdir}/note.inc"
209 remote_download host ${srcdir}/${subdir}/${asm-note}.inc ${subdir}/note.inc
211 if { [string equal ${asm-flags} ""] } {
212 set asm-flags "-I${srcdir}/${subdir} -I${objdir}/${subdir}"
215 if { [string equal ${debug-flags} ""] } {
216 set debug-flags "-gstabs"
219 # Allow the target board to override the debug flags.
220 if { [board_info $dest exists debug_flags] } then {
221 set debug-flags "[board_info $dest debug_flags]"
224 # The debug flags are in the format that gcc expects:
225 # "-gdwarf-2", "-gstabs+", or "-gstabs". To be compatible with the
226 # other languages in the test suite, we accept this input format.
227 # So the user can run the test suite with:
229 # runtest --target_board unix/gdb:debug_flags=-gdwarf-2
230 # make check RUNTESTFLAGS="--target_board unix/gdb:debug_flags=-gdwarf-2"
232 # However, the GNU assembler has different spellings than gcc.
233 # So I adjust the debug flags here.
235 # The GNU assembler spells "dwarf-2" as "dwarf2".
236 regsub "--" "-gdwarf-2" "${debug-flags}" "-gdwarf2" debug-flags
238 # The GNU assembler before 2.15 did not support "stabs+".
239 regsub "--" "-gstabs\[+\]" "${debug-flags}" "-gstabs" debug-flags
241 # The GNU assembler does not support level options like "-g2" or "-g3".
242 regsub "--" "-g\[0-9\]" "${debug-flags}" "" debug-flags
244 if {[target_assemble ${srcdir}/${subdir}/${srcfile1} asmsrc1.o "${asm-flags} ${debug-flags}"] != ""} then {
245 untested asm-source.exp
248 if {[target_assemble ${srcdir}/${subdir}/${srcfile2} asmsrc2.o "${asm-flags} ${debug-flags}"] != ""} then {
249 untested asm-source.exp
253 # We deliberately don't use gdb_compile here to link together the
254 # assembled object files. Using gdb_compile, and therefore the C
255 # compiler, is conceptually wrong, since we're testing raw assembler
256 # code here that provides its own startup code. Using target_link
257 # also avoids a lot of problems on many systems, most notably on
258 # *-*-*bsd* and *-*-solaris2*.
259 if {[target_link "asmsrc1.o asmsrc2.o" "${binfile}" ${link-flags}] != "" } then {
260 untested asm-source.exp
264 # Restore the target board linker script for HC11/HC12.
265 if { [istarget "m6811-*-*"] || [istarget "m6812-*-*"] } {
266 set_board_info ldscript $old_ldscript
269 remote_exec build "mv asmsrc1.o asmsrc2.o ${objdir}/${subdir}"
271 # Collect some line numbers.
272 set line_main [expr [gdb_get_line_number "main start" "asmsrc1.s"] + 1]
273 set line_call_foo2 [expr [gdb_get_line_number "call foo2" "asmsrc1.s"] + 1]
274 set line_search_comment [expr [gdb_get_line_number "search" "asmsrc1.s"] + 1]
275 set line_foo3 [expr [gdb_get_line_number "foo3 start" "asmsrc1.s"] + 1]
276 set line_main_exit [expr [gdb_get_line_number "main exit" "asmsrc1.s"] + 1]
277 set line_foo2 [expr [gdb_get_line_number "foo2 start" "asmsrc2.s"] + 1]
278 set line_call_foo3 [expr [gdb_get_line_number "call foo3" "asmsrc2.s"] + 1]
279 set line_call_foo3_again [expr $line_call_foo3 + 1]
280 set line_foo2_leave [expr [gdb_get_line_number "foo2 leave" "asmsrc2.s"] + 1]
283 gdb_reinitialize_dir $srcdir/$subdir
287 # Run to `main' where we begin our tests.
290 if ![runto_main] then {
294 # Execute the `f' command and see if the result includes source info.
295 gdb_test "f" "asmsrc1\[.\]s:$line_main.*several_nops" "f at main"
297 # See if we properly `next' over a macro with several insns.
298 gdb_test "n" "$line_call_foo2\[ \]*.*foo2" "next over macro"
300 # See if we can properly `step' into a subroutine call.
301 gdb_test "s" "$line_foo2\[ \]*.*" "step into foo2"
303 # Test 'info target', and incidentally capture the entry point address.
305 gdb_test_multiple "info target" "info target" {
306 -re "Symbols from .*asm-source.*Entry point: 0x(\[01232456789abcdefABCDEF\]+).*$gdb_prompt $" {
307 set entry_point $expect_out(1,string)
312 # Capture the start symbol (may be '_start' or 'start')
314 gdb_test_multiple "info symbol 0x$entry_point" "info symbol" {
315 -re "info symbol 0x$entry_point\[\r\n\]+(\[^\r\n\]*) in section .*$gdb_prompt $" {
316 # We match the echoed `info symbol' command here, to help us
317 # reliably identify the beginning of the start symbol in the
318 # command's output. You might think we could just use '^' to
319 # start matching at the beginning of the line, but
320 # unfortunately, in Expect, '^' matches the beginning of the
321 # input that hasn't been matched by any expect clause yet. If
322 # every expect clause consumes a complete line, along with its
323 # terminating CR/LF, this is equivalent to the beginning of a
324 # line. But expect clauses that end with `.*' will consume as
325 # much as happened to arrive from the TTY --- exactly where
326 # they leave you depends on inter-process timing. :(
327 set entry_symbol $expect_out(1,string)
332 # Now try a 'list' from the other source file.
333 gdb_test "list $entry_symbol" ".*gdbasm_startup.*" "list"
335 # Now try a source file search
336 gdb_test "search A routine for foo2 to call" \
337 "$line_search_comment\[ \t\]+comment \"A routine for foo2 to call.\"" "search"
339 # See if `f' prints the right source file.
340 gdb_test "f" ".*asmsrc2\[.\]s:$line_foo2.*" "f in foo2"
342 # `next' one insn (or macro) to set up our stackframe (for the following bt).
343 gdb_test "n" "$line_call_foo3\[ \]*.*foo3" "n in foo2"
345 # See if a simple `bt' prints the right source files and
346 # doesn't fall off the stack.
349 "\#0.*foo2.*asmsrc2\[.\]s:$line_call_foo3.*\#1.*main.*asmsrc1\[.\]s:$line_call_foo2" \
352 # See if a capped `bt' prints the right source files.
353 gdb_test "bt 2" "\#0.*foo2.*asmsrc2\[.\]s:$line_call_foo3.*\#1.*main.*asmsrc1\[.\]s:$line_call_foo2.*" "bt 2 in foo2"
355 # Step into another subroutine which lives back in the first source file.
356 gdb_test "s" ".*" "s 2"
358 # Next over insns to set up the stack frame.
359 gdb_test "n" ".*" "n 2"
361 # Now see if a capped `bt' is correct.
362 gdb_test "bt 3" "\#0.*foo3.*asmsrc1\[.\]s:$line_foo3.*\#1.*foo2.*asmsrc2\[.\]s:$line_call_foo3.*\#2.*main.*asmsrc1\[.\]s:$line_call_foo2.*" "bt 3 in foo3"
364 # Try 'info source' from asmsrc1.s
365 gdb_test "info source" \
366 "Current source file is .*asmsrc1.s.*Source language is asm.*" \
367 "info source asmsrc1.s"
369 # Try 'finishing' from foo3
370 # Some architectures will have one or more instructions after the
371 # call instruction which still is part of the call sequence, so we
372 # must be prepared for a "finish" to show us the caller line
373 # again as well as the statement after.
374 gdb_test_multiple "finish" "finish from foo3" {
375 -re "Run till exit from.*\[\r\n\]$line_call_foo3\[ \t\]+gdbasm_call foo3.*$gdb_prompt $" {
376 pass "finish from foo3"
377 gdb_test "s" ".*" "s after finish"
379 -re "Run till exit from.*\[\r\n\]$line_call_foo3_again\[ \t\]+gdbasm_call foo3.*$gdb_prompt $" {
380 pass "finish from foo3"
384 # Try 'info source' from asmsrc2.s
385 gdb_test "info source" \
386 "Current source file is .*asmsrc2.s.*Source language is asm.*" \
387 "info source asmsrc2.s"
389 # Try 'info sources'. This can produce a lot of output on systems
390 # with dynamic linking, where the system's shared libc was compiled
391 # with debugging info; for example, on Linux, this produces 47kb of
392 # output. So we consume it as we go.
395 gdb_test_multiple "info sources" "info sources" {
396 -re "^\[^,\]*asmsrc1.s(, |\[\r\n\]+)" {
400 -re "^\[^,\]*asmsrc2.s(, |\[\r\n\]+)" {
407 -re "$gdb_prompt $" {
408 if {$seen_asmsrc_1 && $seen_asmsrc_2} {
418 gdb_test "info line" \
419 "Line $line_call_foo3_again of.*asmsrc2.s.*starts at.*<\\.?foo2+.*> and ends at.*<\\.?foo2+.*>." \
422 # Try 'nexting' over next call to foo3
423 gdb_test "next" "$line_foo2_leave\[ \t\]+gdbasm_leave" "next over foo3"
425 # Try 'return' from foo2
426 # Like "finish", "return" command also can return to the caller
427 # line again or the statement after, depending on the architecture.
428 gdb_test_multiple "return" "return from foo2" {
429 -re "Make (foo2|selected stack frame) return now\?.*" {
433 -re "\#0.*main .*$line_call_foo2\[ \t\]+gdbasm_call foo2.*$gdb_prompt $" {
434 pass "return from foo2"
435 gdb_test "s" ".*" "s after return"
437 -re "\#0.*main .*$line_main_exit\[ \t\]+gdbasm_exit0.*$gdb_prompt $" {
438 pass "return from foo2"
442 # Disassemble something, check the output
443 proc test_dis { command var } {
445 gdb_test_multiple "${command}" "${command}" {
446 -re "${var}.*:.*(Cannot access|Bad address)" {
447 # The "disassembler" was only accessing the local
448 # executable and that would cause attempts to disassemble
449 # variables to fail (memory not valid).
450 fail "${command} (memory read error)"
452 -re "${var}.*:.*${gdb_prompt}" {
458 # See if we can look at a global variable, three ways
459 gdb_test "print globalvar" ".* = 11" "look at global variable"
460 test_dis "x/i &globalvar" "globalvar"
461 test_dis "disassem &globalvar, &globalvar+1" "globalvar"
463 # See if we can look at a static variable, three ways
464 gdb_test "print staticvar" ".* = 5" "look at static variable"
465 test_dis "x/i &staticvar" "staticvar"
466 test_dis "disassem &staticvar, &staticvar+1" "staticvar"
468 # See if we can look at a static function
469 gdb_test "disassem foostatic" ".*<\\+0>:.*End of assembler dump." \
470 "look at static function"
472 remote_exec build "rm -f ${subdir}/arch.inc"
473 remote_exec build "rm -f ${subdir}/note.inc"