Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: GDB Patches <gdb-patches@sources.redhat.com>,
	        Daniel Jacobowitz <drow@false.org>
Subject: [RFA] Run follow-fork tests on Linux
Date: Sat, 26 Nov 2005 00:05:00 -0000	[thread overview]
Message-ID: <4387914C.1000404@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 173 bytes --]

This allows the tests "foll-fork" and "foll-vfork" to run on Linux,
where they mostly pass.  A little more verbose output from linux-nat.c
will fix the remaining failures.


[-- Attachment #2: testfork --]
[-- Type: text/plain, Size: 1676 bytes --]

2005-11-25  Michael Snyder  <msnyder@redhat.com>

	* gdb.base/foll-fork.exp: Run if istarget linux.
	Add PASS cases for linux.
	* gdb.base/foll-vfork.exp: Run if istarget linux.

Index: gdb.base/foll-vfork.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/foll-vfork.exp,v
retrieving revision 1.3
diff -p -r1.3 foll-vfork.exp
*** gdb.base/foll-vfork.exp	11 Dec 2002 02:04:45 -0000	1.3
--- gdb.base/foll-vfork.exp	25 Nov 2005 22:30:44 -0000
*************** if  { [gdb_compile "${srcdir}/${subdir}/
*** 55,61 ****
  # Until "set follow-fork-mode" and "catch vfork" are implemented on
  # other targets...
  #
! if ![istarget "hppa*-hp-hpux*"] then {
      continue
  }
  
--- 55,61 ----
  # Until "set follow-fork-mode" and "catch vfork" are implemented on
  # other targets...
  #
! if {![istarget "hppa*-hp-hpux*"] && ![istarget "*-pc-linux*"]} then {
      continue
  }
  
*************** proc vfork_parent_follow_to_bp {} {
*** 109,115 ****
     }
     send_gdb "continue\n"
     gdb_expect {
!       -re ".*Detaching after fork from process.*Breakpoint.*18.*$gdb_prompt "\
                        {pass "vfork parent follow, to bp"}
        -re "$gdb_prompt $" {fail "vfork parent follow, to bp"}
        timeout         {fail "(timeout) vfork parent follow, to bp" }
--- 109,115 ----
     }
     send_gdb "continue\n"
     gdb_expect {
!       -re ".*Detaching after fork from.*Breakpoint.*18.*$gdb_prompt "\
                        {pass "vfork parent follow, to bp"}
        -re "$gdb_prompt $" {fail "vfork parent follow, to bp"}
        timeout         {fail "(timeout) vfork parent follow, to bp" }

             reply	other threads:[~2005-11-25 22:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-26  0:05 Michael Snyder [this message]
2005-11-26  3:58 ` Andreas Schwab
2005-11-28  8:26   ` Michael Snyder
2005-11-26  4:01 ` Mark Kettenis
2005-11-28 13:01   ` Michael Snyder
2005-11-26  4:03 ` Daniel Jacobowitz
2005-11-28 14:00   ` 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=4387914C.1000404@redhat.com \
    --to=msnyder@redhat.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    /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