From: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [PATCH][cr-tests] Ensure pthread stack attributes are restored
Date: Fri, 11 Dec 2009 17:53:51 -0800 [thread overview]
Message-ID: <20091212015350.GA11487@us.ibm.com> (raw)
In-Reply-To: <20091211153402.GA28867-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Serge E. Hallyn [serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org] wrote:
| Quoting Sukadev Bhattiprolu (sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org):
| > +++ b/process-tree/run-pthread2.sh
| > @@ -0,0 +1,206 @@
| > +#!/bin/bash
| > +
| > +source ../common.sh
| > +
| > +#dir=`mktemp -p . -d -t cr_pthread2_XXXXXXX` || (echo "mktemp failed"; exit 1)
| > +dir=cr_pthread2
|
| Note that this means we won't be able to run multiple instances in
| parallel. Why did you need to do this?
|
Grr, I meant to remove that after my testing.
Anyway, I am wondering if I should just extend the test case to memcmp()
the pthread_attr_t before and after C/R rather than individually testing
each attribute (like the stack addr/size in this case). I am working on
an update to this test and will fix this too.
Sukadev
prev parent reply other threads:[~2009-12-12 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 4:11 [PATCH][cr-tests] Ensure pthread stack attributes are restored Sukadev Bhattiprolu
[not found] ` <20091211041126.GC20947-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-12-11 15:20 ` Serge E. Hallyn
2009-12-11 15:34 ` Serge E. Hallyn
[not found] ` <20091211153402.GA28867-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-12-12 1:53 ` Sukadev Bhattiprolu [this message]
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=20091212015350.GA11487@us.ibm.com \
--to=sukadev-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
/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