public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: "Mitani" <mitani@ryobi.co.jp>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] nanosleep testcase problem
Date: Mon, 4 Jan 2010 14:07:55 +0900	[thread overview]
Message-ID: <000001ca8cfb$e04fb340$a0ef19c0$@co.jp> (raw)

Hi,

I want to wish you happy new year.


------

By the way, I found a new problem with the "nanosleep02" testcase.

"main()" function executes fork(), and child process calls "do_child()"
function.
"do_child()" function must be ended by "exit()". But in "nanosleep02"
testcase, there is a case in which "exit()" isn't executed.
Therefore, the child process lives after "do_child()" function, 
and it executes "wait()" function which must be executed in parent
process only.

Here is the patch fixes these problem:

============
--- nanosleep02.c	2009-12-23 02:35:13.000000000 +0900
+++ nanosleep02.c.new	2010-01-04 10:15:08.000000000 +0900
@@ -277,6 +277,9 @@
 		tst_resm(TPASS, "call succeeded");
 		exit(0);
 	}
+	
+	/* Everything is fine, exit normally */
+	exit(0);
 }
 
 /*
============


Regards--


-Tomonori Mitani



------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2010-01-04  5:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04  5:07 Mitani [this message]
2010-01-04 14:55 ` [LTP] nanosleep testcase problem Michal Simek
2010-01-06  6:07   ` Garrett Cooper

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='000001ca8cfb$e04fb340$a0ef19c0$@co.jp' \
    --to=mitani@ryobi.co.jp \
    --cc=ltp-list@lists.sourceforge.net \
    /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