From: Berthold Gunreben <b.gunreben@web.de>
To: "linux-parisc" <linux-parisc@vger.kernel.org>
Subject: Re: vfork test case.
Date: Thu, 17 Dec 2009 22:40:22 +0100 [thread overview]
Message-ID: <200912172240.22252.b.gunreben@web.de> (raw)
In-Reply-To: <119aab440912061319y5b863203ve5dc3dc568a6ccec@mail.gmail.com>
Hi Carlos,
On Sunday 06 December 2009 22:19:13 Carlos O'Donell wrote:
> Kyle, James,
>
> I have constructed a vfork test case which shows some of the problems
> I have using vfork reliably. This fails every time on my PA8700 system
> running 2.6.32-rc6. It appears as though r28 (ret0) in the parent is
> being corrupted.
this reminds me of a problem with vfork that I encountered some years ago. The
problem as described in
http://sourceware.org/ml/libc-alpha/2003-02/msg00042.html
was fixed for many architectures, but not for hppa as far as I remember. See
also
http://sourceware.org/ml/libc-hacker/2003-02/msg00015.html
I have no idea if this is related, but thought it won't hurt to mention this.
Berthold
next prev parent reply other threads:[~2009-12-17 21:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 21:19 vfork test case Carlos O'Donell
2009-12-15 22:21 ` John David Anglin
2009-12-16 13:24 ` Carlos O'Donell
2009-12-16 21:22 ` Helge Deller
2009-12-16 21:35 ` John David Anglin
2009-12-17 14:24 ` Carlos O'Donell
2009-12-17 16:45 ` dann frazier
2009-12-17 19:12 ` Helge Deller
2009-12-17 20:39 ` Carlos O'Donell
2009-12-19 20:44 ` Grant Grundler
2009-12-17 21:40 ` Berthold Gunreben [this message]
2009-12-17 21:59 ` Carlos O'Donell
2010-06-20 4:28 ` John David Anglin
2010-06-22 15:17 ` Carlos O'Donell
2010-06-22 15:39 ` Carlos O'Donell
2010-06-22 22:50 ` John David Anglin
2010-06-27 15:41 ` Carlos O'Donell
2010-06-22 16:26 ` John David Anglin
2010-06-22 18:34 ` Carlos O'Donell
2010-06-22 18:44 ` John David Anglin
2010-06-22 19:53 ` Carlos O'Donell
2010-06-22 20:20 ` John David Anglin
2010-06-22 21:13 ` Carlos O'Donell
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=200912172240.22252.b.gunreben@web.de \
--to=b.gunreben@web.de \
--cc=linux-parisc@vger.kernel.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