From: "Jakob Engblom" <jakob@virtutech.com>
To: <gdb-patches@sourceware.org>
Subject: RE: GDB MI Reverse Commands added [3 of 3]
Date: Mon, 31 Aug 2009 13:13:00 -0000 [thread overview]
Message-ID: <010001ca2a3b$d86846b0$8938d410$@com> (raw)
In-Reply-To: <4A95DDD6.2000200@vmware.com>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
Updated the reflect Michael Snyder's comment on the copyright date.
Changelog:
testsuite/gdb.mi/
* mi2-reverse.exp: New file. Test for reverse option to the following MI
commands: exec-continue, exec-finish, exec-next, exec-step,
exec-next-instruction, exec-step-instruction. (liangyi@newfield-tech.com)
Best regards,
/jakob
_______________________________________________________
Jakob Engblom, PhD, Technical Marketing Manager
Virtutech Direct: +46 8 690 07 47
Drottningholmsvägen 22 Mobile: +46 709 242 646
11243 Stockholm Web: www.virtutech.com
Sweden
________________________________________________________
[-- Attachment #2: mi2-reverse.exp --]
[-- Type: application/octet-stream, Size: 6000 bytes --]
# Copyright 2009
# Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
# Test Machine interface (MI) operations
# Verify that, using the MI, we can run a simple program in both forward
# and reverse directions with the following execution commands:
# - exec-continue
# - exec-finish
# - exec-next
# - exec-step
# - exec-next-instruction
# - exec-step-instruction
# The goal is not to test gdb functionality, which is done by other tests,
# but to verify the correct output response to MI operations.
#
if ![target_info exists gdb,can_reverse] {
return
}
load_lib mi-support.exp
set MIFLAGS "-i=mi2"
gdb_exit
if [mi_gdb_start] {
continue
}
set testfile "basics"
set srcfile ${testfile}.c
set binfile ${objdir}/${subdir}/mi2-reverse
if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug additional_flags=-DFAKEARGV}] != "" } {
untested mi2-reverse.exp
return -1
}
mi_run_to_main
if [target_info exists gdb,use_precord] {
# Activate process record/replay
if [mi_gdb_test "-interpreter-exec console record" \
{\^done} "Turn on process record"] {
warning "Fail to activate process record/replay, tests in this group will not be performed.\n";
return -1
}
}
# Locate line numbers in basics.c.
set line_callee4_head [gdb_get_line_number "callee4 ("]
set line_callee4_body [expr $line_callee4_head + 2]
set line_callee3_head [gdb_get_line_number "callee3 ("]
set line_callee3_body [expr $line_callee3_head + 2]
set line_callee3_close [expr $line_callee3_head + 3]
set line_callee2_head [gdb_get_line_number "callee2 ("]
set line_callee2_body [expr $line_callee2_head + 2]
set line_callee2_close [expr $line_callee2_head + 3]
set line_callee1_head [gdb_get_line_number "callee1 ("]
set line_callee1_body [expr $line_callee1_head + 2]
set line_callee1_close [expr $line_callee1_head + 3]
set line_callme_head [gdb_get_line_number "callme"]
set line_callme_body [expr $line_callme_head + 2]
set line_main_head [gdb_get_line_number "main ("]
set line_main_body [expr $line_main_head + 2]
set line_main_hello [gdb_get_line_number "Hello, World!"]
set line_main_callme_1 [gdb_get_line_number "callme (1"]
# Forward execute to the callme() function, so that we can
# execute backward from there.
mi_continue_to callme
mi_delete_breakpoints
proc test_controlled_execution_reverse {} {
global mi_gdb_prompt
global srcfile
global hex
global line_callee4_head line_callee4_body
global line_callee3_head line_callee3_body line_callee3_close
global line_callee2_head line_callee2_body line_callee2_close
global line_callee1_head line_callee1_body line_callee1_close
global line_main_head line_main_body
global line_main_hello line_main_callme_1
# Test exec-reverse-finish
mi_execute_to "exec-finish --reverse" \
"end-stepping-range" "main" "" \
"basics.c" $line_main_callme_1 "" \
"reverse finish from callme"
# Test exec-reverse-next
# FIXME: Why does it take 2 next commands to get back to the
# previous line?
mi_execute_to "exec-next --reverse 2" \
"end-stepping-range" "main" "" \
"basics.c" $line_main_hello "" \
"reverse next to get over the call to do_nothing"
# Test exec-reverse-step
mi_execute_to "exec-step --reverse" \
"end-stepping-range" "callee1" \
"\{name=\"intarg\",value=\"2\"\},\{name=\"strarg\",value=\"$hex \\\\\"A string argument\.\\\\\"\"\},\{name=\"fltarg\",value=\"3.5\"\}" \
"basics.c" $line_callee1_close "" \
"reverse step to callee1"
mi_execute_to "exec-step --reverse" \
"end-stepping-range" "callee2" \
"\{name=\"intarg\",value=\"2\"\},\{name=\"strarg\",value=\"$hex \\\\\"A string argument\.\\\\\"\"\}" \
"basics.c" $line_callee2_close "" \
"reverse step to callee2"
mi_execute_to "exec-step --reverse" \
"end-stepping-range" "callee3" \
"\{name=\"strarg\",value=\"$hex \\\\\"A string argument\.\\\\\"\"\}" \
"basics.c" $line_callee3_close "" \
"reverse step to callee3"
mi_execute_to "exec-step --reverse" \
"end-stepping-range" "callee4" "" \
"basics.c" "\[0-9\]+" "" \
"reverse step to callee4"
# Test exec-reverse-[step|next]-instruction
mi_execute_to "exec-step-instruction --reverse" \
"end-stepping-range" "callee4" "" \
"basics.c" "\[0-9\]+" "" \
"reverse-step-instruction at callee4"
mi_execute_to "exec-next-instruction --reverse" \
"end-stepping-range" "callee4" "" \
"basics.c" "\[0-9\]+" "" \
"reverse-next-instruction at callee4"
# Test exec-reverse-continue
mi_create_breakpoint "-t basics.c:$line_callee3_head" \
3 del callee3 ".*basics.c" $line_callee3_head $hex \
"insert temp breakpoint at basics.c:$line_callee3_head"
mi_execute_to "exec-continue --reverse" \
"breakpoint-hit" "callee3" \
"\{name=\"strarg\",value=\"$hex \\\\\"A string argument\.\\\\\"\"\}" \
"basics.c" "\[0-9\]+" \
{ "" "disp=\"del\""} \
"reverse-continue at callee3"
mi_execute_to "exec-continue --reverse" \
"" "main" "" \
"basics.c" $line_main_body "" \
"reverse-continue at main"
}
test_controlled_execution_reverse
mi_gdb_exit
return 0
next prev parent reply other threads:[~2009-08-31 13:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 15:10 Jakob Engblom
2009-08-27 1:43 ` Michael Snyder
2009-08-31 13:13 ` Jakob Engblom [this message]
2009-09-01 12:48 ` Jakob Engblom
2009-09-01 17:36 ` Tom Tromey
2009-09-07 1:18 ` Michael Snyder
2009-09-07 7:10 ` Jakob Engblom
2009-09-07 18:09 ` Joel Brobecker
2009-09-08 7:11 ` Jakob Engblom
2009-09-02 8:23 ` Vladimir Prus
2009-09-03 18:44 ` Jakob Engblom
2009-09-03 20:13 ` Michael Snyder
2009-09-07 1:44 ` Hui Zhu
2009-12-15 19:43 ` Michael Snyder
2009-12-16 9:59 ` Vladimir Prus
2009-12-15 19:42 ` Michael Snyder
2009-12-16 8:06 ` Vladimir Prus
2009-12-16 8:48 ` Jakob Engblom
2009-12-16 10:05 ` Vladimir Prus
2010-02-12 21:39 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='010001ca2a3b$d86846b0$8938d410$@com' \
--to=jakob@virtutech.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox