Bug 13796 - disp-step-syscall.exp: vfork
Summary: disp-step-syscall.exp: vfork
Alias: None
Product: gdb
Classification: Unclassified
Component: server (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
Depends on: 13584
  Show dependency treegraph
Reported: 2012-03-03 06:49 UTC by Jan Kratochvil
Modified: 2016-02-18 13:03 UTC (History)
2 users (show)

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Jan Kratochvil 2012-03-03 06:49:54 UTC
After fixing gdb.base/disp-step-syscall.exp to properly test what it tests it has revealed:

Program terminated with signal SIGILL, Illegal instruction.
The program no longer exists.
(gdb) PASS: gdb.base/disp-step-syscall.exp: vfork: single step over vfork
Child terminated with signal = 0x4 (SIGILL)
GDBserver exiting
print /x $pc
No registers.
(gdb) FAIL: gdb.base/disp-step-syscall.exp: vfork: get hexadecimal valueof "$pc" (timeout)

It works with linux-nat so it seems like a gdbserver (and not kernel) issue.
Comment 1 cvs-commit@gcc.gnu.org 2012-03-03 06:58:22 UTC
CVSROOT:	/cvs/src
Module name:	src
Changes by:	jkratoch@sourceware.org	2012-03-03 06:58:16

Modified files:
	gdb/testsuite  : ChangeLog 
	gdb/testsuite/gdb.base: disp-step-syscall.exp 

Log message:
	Setup KFAIL for PR server/13796.
	* gdb.base/disp-step-syscall.exp (single step over vfork): Setup KFAIL.

Comment 2 Pedro Alves 2012-03-03 15:22:59 UTC
The test displace-steps over a vfork syscall.  In the special case of displace-stepping over a (v)fork, GDB needs to adjust both the parent and the child back from the displace stepping scratchpad.   Since GDBserver doesn't support following (v)forks yet, gdb is never informed about the child, and so the child
ends up continuing freely, unadjusted, from the scratchpad, and crashes.
Comment 3 Pedro Alves 2012-03-06 19:09:47 UTC
Actually, I just found my note that says:

"We miss adjusting the child, and then the parent gets corrupted, and crashes."

which makes a bit more sense, given we see the crash with vfork.
Comment 4 cvs-commit@gcc.gnu.org 2016-02-18 13:03:08 UTC
The master branch has been updated by Yao Qi <qiyao@sourceware.org>:


commit 2d5189bd3a6e2014b9b42a4bcb0df410eff1c2e1
Author: Yao Qi <yao.qi@linaro.org>
Date:   Thu Feb 18 13:02:12 2016 +0000

    Remove setup_kfail server/13796 in disp-step-syscall.exp
    This patch series add fork support in target remote,
      [PATCH v2 0/3] Target remote mode fork and exec support
    so GDB can be informed about the child, and adjust child correctly in
    displaced stepping.  The PR server/13796 was fixed by this patch
    series actually.  Test results on buildbot show this KFAIL->KPASS
    change https://sourceware.org/ml/gdb-testers/2015-q4/msg10128.html
    2016-02-18  Yao Qi  <yao.qi@linaro.org>
    	* gdb.base/disp-step-syscall.exp (disp_step_cross_syscall):
    	Don't call setup_kfail.
Comment 5 Yao Qi 2016-02-18 13:03:50 UTC
This bug was fixed by this patch series,

  [PATCH v2 0/3] Target remote mode fork and exec support

Close it.