From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/8] foll-vfork.exp: Don't hard code line numbers.
Date: Thu, 25 Oct 2012 17:42:00 -0000 [thread overview]
Message-ID: <20121025174205.13324.4808.stgit@brno.lan> (raw)
In-Reply-To: <20121025174002.13324.8164.stgit@brno.lan>
The test hard codes line numbers, which makes it fragile wrt to
changes to the test's sources. This replaces all the hard-coded
numbers with something else.
gdb/testsuite/
2012-10-25 Pedro Alves <palves@redhat.com>
Don't hard code line numbers.
* gdb.base/foll-vfork.exp (vfork_parent_follow_through_step):
Expect text from the sources instead of a line number.
(vfork_parent_follow_to_bp)
(vfork_and_exec_child_follow_to_main_bp)
(vfork_and_exec_child_follow_through_step)
(tcatch_vfork_then_parent_follow, tcatch_vfork_then_child_follow):
Use gdb_get_line_number.
---
gdb/testsuite/gdb.base/foll-vfork.exp | 26 ++++++++++++++++++--------
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/gdb/testsuite/gdb.base/foll-vfork.exp b/gdb/testsuite/gdb.base/foll-vfork.exp
index 73be334..67d077d 100644
--- a/gdb/testsuite/gdb.base/foll-vfork.exp
+++ b/gdb/testsuite/gdb.base/foll-vfork.exp
@@ -91,7 +91,7 @@ proc vfork_parent_follow_through_step {} {
set test "vfork parent follow, through step"
gdb_test_multiple "next" $test {
- -re "Detaching after fork from.*13.*$gdb_prompt " {
+ -re "Detaching after fork from.*if \\(pid == 0\\).*$gdb_prompt " {
pass "vfork parent follow, through step"
}
}
@@ -109,11 +109,12 @@ proc vfork_parent_follow_to_bp {} {
gdb_test_no_output "set follow-fork parent" \
"set follow-fork parent, vfork to bp"
- gdb_test "break ${srcfile}:18" ".*" "break, vfork to bp"
+ set bp_location [gdb_get_line_number "printf (\"I'm the proud parent of child"]
+ gdb_test "break ${srcfile}:${bp_location}" ".*" "break, vfork to bp"
set test "vfork parent follow, to bp"
gdb_test_multiple "continue" $test {
- -re ".*Detaching after fork from child process.*Breakpoint.*18.*$gdb_prompt " {
+ -re ".*Detaching after fork from child process.*Breakpoint.*${bp_location}.*$gdb_prompt " {
pass $test
}
}
@@ -153,14 +154,17 @@ proc kill_child {} {
proc vfork_and_exec_child_follow_to_main_bp {} {
global gdb_prompt
+ global srcfile2
gdb_test_no_output \
"set follow-fork child" \
"set follow-fork child, vfork and exec to main bp"
+ set linenum [gdb_get_line_number "printf(\"Hello from vforked-prog" ${srcfile2}]
+
set test "vfork and exec child follow, to main bp"
gdb_test_multiple "continue" $test {
- -re "Attaching after.* vfork to.*xecuting new program.*Breakpoint.*vforked-prog.c:9.*$gdb_prompt " {
+ -re "Attaching after.* vfork to.*xecuting new program.*Breakpoint.*vforked-prog.c:${linenum}.*$gdb_prompt " {
pass $test
}
}
@@ -177,6 +181,7 @@ proc vfork_and_exec_child_follow_to_main_bp {} {
proc vfork_and_exec_child_follow_through_step {} {
global gdb_prompt
+ global srcfile2
# This test cannot be performed prior to HP-UX 10.30, because ptrace-based
# debugging of a vforking program basically doesn't allow the child to do
@@ -195,8 +200,9 @@ proc vfork_and_exec_child_follow_through_step {} {
"set follow-fork child, vfork and exec through step"
set test "vfork and exec child follow, through step"
+ set linenum [gdb_get_line_number "printf(\"Hello from vforked-prog" ${srcfile2}]
gdb_test_multiple "next" $test {
- -re "Attaching after fork to.*Executing new program.*Breakpoint.*vforked-prog.c:9.*$gdb_prompt " {
+ -re "Attaching after fork to.*Executing new program.*Breakpoint.*vforked-prog.c:${linenum}.*$gdb_prompt " {
pass "$test"
}
}
@@ -235,9 +241,10 @@ proc tcatch_vfork_then_parent_follow {} {
}
}
+ set linenum [gdb_get_line_number "pid = vfork ();"]
set test "vfork parent follow, finish after tcatch vfork"
gdb_test_multiple "finish" $test {
- -re "Run till exit from.*vfork.*0x\[0-9a-fA-F\]* in main .* at .*${srcfile}:12.*$gdb_prompt " {
+ -re "Run till exit from.*vfork.*0x\[0-9a-fA-F\]* in main .* at .*${srcfile}:${linenum}.*$gdb_prompt " {
pass $test
}
-re "Run till exit from.*__kernel_v?syscall.*0x\[0-9a-fA-F\]* in vfork .*$gdb_prompt " {
@@ -277,16 +284,19 @@ proc tcatch_vfork_then_child_follow {} {
}
}
+ set linenum1 [gdb_get_line_number "pid = vfork ();"]
+ set linenum2 [gdb_get_line_number "printf(\"Hello from vforked-prog" ${srcfile2}]
+
set test "vfork child follow, finish after tcatch vfork"
gdb_test_multiple "finish" $test {
- -re "Run till exit from.*vfork.*${srcfile}:12.*$gdb_prompt " {
+ -re "Run till exit from.*vfork.*${srcfile}:${linenum1}.*$gdb_prompt " {
pass $test
}
-re "Run till exit from.*__kernel_v?syscall.*0x\[0-9a-fA-F\]* in vfork .*$gdb_prompt " {
send_gdb "finish\n"
exp_continue
}
- -re "Run till exit from.*vfork.*${srcfile2}:9.*$gdb_prompt " {
+ -re "Run till exit from.*vfork.*${srcfile2}:${linenum2}.*$gdb_prompt " {
pass "$test (followed exec)"
}
}
next prev parent reply other threads:[~2012-10-25 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 17:42 [PATCH 0/8] Fix PR gdb/14766; cleanup foll-vfork.exp and extend it Pedro Alves
2012-10-25 17:42 ` [PATCH 7/8] foll-vfork.exp: Also test following vfork when the child exits Pedro Alves
2012-10-25 17:42 ` Pedro Alves [this message]
2012-10-25 17:42 ` [PATCH 6/8] foll-vfork.exp: Clean restart gdb before each test procedure Pedro Alves
2012-11-02 18:18 ` Pedro Alves
2012-10-25 17:42 ` [PATCH 5/8] foll-vfork.exp: Use with_test_prefix Pedro Alves
2012-10-25 17:42 ` [PATCH 8/8] Fix PR gdb/14766 - vfork child exit with "set follow-fork-mode child" broken Pedro Alves
2012-10-25 17:49 ` Pedro Alves
2012-10-25 17:42 ` [PATCH 4/8] foll-vfork.c/vforked-prog.c: Add copyright headers Pedro Alves
2012-10-25 17:42 ` [PATCH 3/8] foll-vfork.exp: Expose more testing on non-HP/UX targets Pedro Alves
2012-10-25 17:42 ` [PATCH 1/8] foll-vfork.exp: Modernize Pedro Alves
2012-10-30 20:50 ` [PATCH 0/8] Fix PR gdb/14766; cleanup foll-vfork.exp and extend it Tom Tromey
2012-11-02 18:15 ` Pedro Alves
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=20121025174205.13324.4808.stgit@brno.lan \
--to=palves@redhat.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