projects / binutils-gdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: add0eb9) | patch
gdb: test vfork + follow-fork-mode=parent + detach-on-fork=off
authorSimon Marchi <simon.marchi@efficios.com>
Mon, 10 Jan 2022 17:50:17 +0000 (12:50 -0500)
committerSimon Marchi <simon.marchi@polymtl.ca>
Thu, 31 Mar 2022 15:08:47 +0000 (11:08 -0400)
commitb6535766233323fb76c235b77792254d80e9ac0b
treefd317350dcec7bebf1f2c3607f10a4bca39def2atree
parentadd0eb9d6e731e08a0bc2463d8c1f0acb02894a0commit | diff
gdb: test vfork + follow-fork-mode=parent + detach-on-fork=off

The particular behavior we have when using that combination of settings
doesn't seem tested at all (at least, I don't find it if I grep for "Can
not resume the parent process").  Add a simple test for that.

Change-Id: Ib9454a615abba661b42f1b15056df73ed1bcd4c5
gdb/testsuite/gdb.base/vfork-follow-parent.c [new file with mode: 0644] blob
gdb/testsuite/gdb.base/vfork-follow-parent.exp [new file with mode: 0644] blob