-# Copyright 1997, 1999, 2007-2012 Free Software Foundation, Inc.
+# Copyright 1997-2017 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
# either execs or exits --- since those events take somewhat different
# code paths in GDB, both variants are exercised.
-if { [is_remote target] || ![isnative] } then {
- continue
-}
-
# Until "set follow-fork-mode" and "catch vfork" are implemented on
# other targets...
#
-if {![istarget "hppa*-hp-hpux*"] && ![istarget "*-linux*"]} then {
+if {![istarget "*-linux*"]} then {
continue
}
-# Test to see if we are on an HP-UX 10.20 and if so,
-# do not run these tests as catching vfork is disabled for
-# 10.20.
-
-if [istarget "hppa*-hp-hpux10.20"] then {
- return 0
-}
-
-# NOTE drow/2002-12-06: I don't know what the referenced kernel problem
-# is, but it appears to be fixed in recent HP/UX versions.
-
-##if [istarget "hppa2.0w-hp-hpux*"] {
-## warning "Don't run gdb.base/foll-vfork.exp until JAGaa43495 kernel problem is fixed."
-## return 0
-##}
-
standard_testfile
-if {[build_executable $testfile.exp $testfile $srcfile {debug}] == -1} {
- untested "failed to compile $testfile"
+set compile_options debug
+
+if {[build_executable $testfile.exp $testfile $srcfile $compile_options] == -1} {
+ untested "failed to compile main testcase"
return -1
}
set testfile2 "vforked-prog"
set srcfile2 ${testfile2}.c
-if {[build_executable $testfile.exp $testfile2 $srcfile2 {debug}] == -1} {
- untested "failed to compile $testfile2"
+if {[build_executable $testfile.exp $testfile2 $srcfile2 $compile_options] == -1} {
+ untested "failed to compile secondary testcase"
return -1
}
# error, behave as "return", so we don't try to continue testing with
# a borked session.
proc setup_gdb {} {
- global testfile
+ global testfile srcfile
clean_restart $testfile
if ![runto_main] {
return -code return
}
+
+ set tbreak_line [gdb_get_line_number " VFORK " $srcfile]
+ gdb_test "tbreak ${tbreak_line}"
+ gdb_continue_to_breakpoint ".*"
}
proc check_vfork_catchpoints {} {
set test "step"
gdb_test_multiple "next" $test {
- -re "Detaching after fork from.*if \\(pid == 0\\).*$gdb_prompt " {
+ -re "Detaching after vfork from.*if \\(pid == 0\\).*$gdb_prompt " {
pass $test
}
}
set test "continue to bp"
gdb_test_multiple "continue" $test {
- -re ".*Detaching after fork from child process.*Breakpoint.*${bp_location}.*$gdb_prompt " {
+ -re ".*Detaching after vfork from child process.*Breakpoint.*${bp_location}.*$gdb_prompt " {
pass $test
}
}
set test "continue to child exit"
gdb_test_multiple "continue" $test {
-re "Couldn't get registers.*$gdb_prompt " {
- setup_kfail "gdb/14766" *-*-*
+ # PR gdb/14766
fail "$test"
}
-re "Attaching after.* vfork to.*Detaching vfork parent .* after child exit.*$gdb_prompt " {
set test "continue to bp"
gdb_test_multiple "continue" $test {
- -re "Attaching after.* vfork to.*xecuting new program.*Breakpoint.*vforked-prog.c:${linenum}.*$gdb_prompt " {
+ -re "Attaching after.* vfork to.*Detaching vfork parent.*xecuting new program.*Breakpoint.*vforked-prog.c:${linenum}.*$gdb_prompt " {
pass $test
}
}
global gdb_prompt
global srcfile2
- if { [istarget "hppa*-*-hpux*"] && ![istarget "hppa*-*-hpux11.*"] } {
- # 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 things like hit a breakpoint between a
- # vfork and exec. This means that saying "set follow-fork
- # child; next" at a vfork() call won't work, because the
- # implementation of "next" sets a "step resume" breakpoint at
- # the return from the vfork(), which the child will hit on its
- # way to exec'ing.
- #
- verbose "vfork child-following next test ignored for pre-HP/UX-10.30 targets."
- return 0
- }
-
setup_gdb
gdb_test_no_output "set follow-fork child"
set test "step over vfork"
- if { [istarget "hppa*-*-hpux*"]} {
- # Since the child cannot be debugged until after it has exec'd,
- # and since there's a bp on "main" in the parent, and since the
- # bp's for the parent are recomputed in the exec'd child, the
- # step through a vfork should land us in the "main" for the
- # exec'd child, too.
- #
- 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:${linenum}.*$gdb_prompt " {
- pass "$test"
- }
- }
- } else {
- # The ideal support is to be able to debug the child even
- # before it execs. Thus, "next" lands on the next line after
- # the vfork.
- gdb_test_multiple "next" $test {
- -re "Attaching after .* vfork to child.*if \\(pid == 0\\).*$gdb_prompt " {
- pass "$test"
- }
+
+ # The ideal support is to be able to debug the child even
+ # before it execs. Thus, "next" lands on the next line after
+ # the vfork.
+ gdb_test_multiple "next" $test {
+ -re "Attaching after .* vfork to child.*if \\(pid == 0\\).*$gdb_prompt " {
+ pass "$test"
}
}
# The parent has been detached; allow time for any output it might
exec sleep 1
}}
+proc continue_to_vfork {} {
+ global gdb_prompt
+
+ # A vfork catchpoint may stop in either "vfork" or "_vfork".
+ set test "continue to vfork"
+ gdb_test_multiple "continue" $test {
+ -re "vfork \\(\\) at .*$gdb_prompt $" {
+ pass $test
+ }
+ -re "0x\[0-9a-fA-F\]*.*(vfork|__kernel_v?syscall).*$gdb_prompt " {
+ pass $test
+ }
+ }
+}
+
proc tcatch_vfork_then_parent_follow {} {
with_test_prefix "vfork parent follow, finish after tcatch vfork" {
global gdb_prompt
gdb_test "tcatch vfork" "Catchpoint .*(vfork).*"
- # HP-UX 10.20 seems to stop you in "vfork", while more recent
- # HP-UXs stop you in "_vfork".
- set test "continue to vfork"
- gdb_test_multiple "continue" $test {
- -re "0x\[0-9a-fA-F\]*.*(vfork|__kernel_v?syscall).*$gdb_prompt " {
- pass $test
- }
- -re "vfork \\(\\) at.*$gdb_prompt " {
- pass $test
- }
- }
+ continue_to_vfork
set linenum [gdb_get_line_number "pid = vfork ();"]
set test "finish"
gdb_test "tcatch vfork" "Catchpoint .*(vfork).*"
- # HP-UX 10.20 seems to stop you in "vfork", while more recent HP-UXs
- # stop you in "_vfork".
- set test "continue to vfork"
- gdb_test_multiple "continue" $test {
- -re "vfork \\(\\) at .*$gdb_prompt $" {
- pass $test
- }
- -re "0x\[0-9a-fA-F\]*.*(vfork|__kernel_v?syscall).*$gdb_prompt " {
- pass $test
- }
- }
+ continue_to_vfork
set linenum1 [gdb_get_line_number "pid = vfork ();"]
set linenum2 [gdb_get_line_number "printf(\"Hello from vforked-prog" ${srcfile2}]
gdb_test "tcatch vfork" "Catchpoint .*(vfork).*"
- # HP-UX 10.20 seems to stop you in "vfork", while more recent HP-UXs
- # stop you in "_vfork".
- set test "continue to vfork"
- gdb_test_multiple "continue" $test {
- -re "vfork \\(\\) at .*$gdb_prompt $" {
- pass $test
- }
- -re "0x\[0-9a-fA-F\]*.*(vfork|__kernel_v?syscall).*$gdb_prompt " {
- pass $test
- }
- }
+ continue_to_vfork
set test "finish"
gdb_test_multiple "finish" $test {
- -re "Couldn't get registers.*$gdb_prompt " {
- setup_kfail "gdb/14766" *-*-*
- fail "$test "
- }
-re "Run till exit from.*vfork.*exited normally.*$gdb_prompt " {
setup_kfail "gdb/14762" *-*-*
fail $test
exec sleep 1
}}
+proc vfork_relations_in_info_inferiors { variant } {
+ with_test_prefix "vfork relations in info inferiors" {
+ global gdb_prompt
+
+ setup_gdb
+
+ gdb_test_no_output "set follow-fork child"
+
+ set test "step over vfork"
+ gdb_test_multiple "next" $test {
+ -re "Attaching after .* vfork to child.*if \\(pid == 0\\).*$gdb_prompt " {
+ pass "$test"
+ }
+ }
+
+ gdb_test "info inferiors" \
+ ".*is vfork parent of inferior 2.*is vfork child of inferior 1" \
+ "info inferiors shows vfork parent/child relation"
+
+ if { $variant == "exec" } {
+ global srcfile2
+
+ set linenum [gdb_get_line_number "printf(\"Hello from vforked-prog" ${srcfile2}]
+ set test "continue to bp"
+ gdb_test_multiple "continue" $test {
+ -re ".*xecuting new program.*Breakpoint.*vforked-prog.c:${linenum}.*$gdb_prompt " {
+ pass $test
+ }
+ }
+ } else {
+ set test "continue to child exit"
+ gdb_test_multiple "continue" $test {
+ -re "exited normally.*$gdb_prompt " {
+ pass $test
+ }
+ }
+ }
+
+ set test "vfork relation no longer appears in info inferiors"
+ gdb_test_multiple "info inferiors" $test {
+ -re "is vfork child of inferior 1.*$gdb_prompt $" {
+ fail $test
+ }
+ -re "is vfork parent of inferior 2.*$gdb_prompt $" {
+ fail $test
+ }
+ -re "$gdb_prompt $" {
+ pass $test
+ }
+ }
+}}
+
proc do_vfork_and_follow_parent_tests {} {
global gdb_prompt
# catchpoints.
# ??rehrauer: NYI. Will add testpoints here when implemented.
#
+
+ # Step over a vfork in the child, do "info inferiors" and check the
+ # parent/child relation is displayed. Run the child over the exec,
+ # and confirm the relation is no longer displayed in "info
+ # inferiors".
+ #
+ vfork_relations_in_info_inferiors "exec"
}
proc do_vfork_and_follow_child_tests_exit {} {
# Try catching a vfork, and stepping out to the child.
#
tcatch_vfork_then_child_follow_exit
+
+ # Step over a vfork in the child, do "info inferiors" and check the
+ # parent/child relation is displayed. Run the child to completion,
+ # and confirm the relation is no longer displayed in "info
+ # inferiors".
+ #
+ vfork_relations_in_info_inferiors "exit"
}
with_test_prefix "check vfork support" {
projects / deliverable / binutils-gdb.git / blobdiff