From: Jes Sorensen <jes@linuxcare.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: pipes
Date: 22 Feb 2001 11:37:22 +0100 [thread overview]
Message-ID: <d3ofvv57h9.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: Alan Modra's message of "Thu, 22 Feb 2001 17:37:55 +1100 (EST)"
>>>>> "Alan" == Alan Modra <alan@linuxcare.com.au> writes:
Alan> Nothing suspicious in previous rt_sigaction calls as far as I
Alan> could see, and putting in a debugging printk in do_sigaction
Alan> shows sa_flags is being set correctly, to 0x40.
I'd start by looking at the parisc kernel and glibc implementation of
pipe(). It's a somewhat special system call since it has two return
values.
I managed to wreck pipe() on the ia64 for a while as well.
Jes
next prev parent reply other threads:[~2001-02-22 10:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 15:29 [parisc-linux] pipes Alan Modra
2001-02-15 16:38 ` Richard Hirst
2001-02-22 6:37 ` [parisc-linux] pipes Alan Modra
2001-02-22 10:37 ` Jes Sorensen [this message]
2001-02-22 11:00 ` Richard Hirst
2001-02-22 11:09 ` Richard Hirst
2001-02-22 11:26 ` Alan Cox
2001-02-22 11:39 ` Alan Modra
2001-02-22 11:52 ` Alan Cox
2001-02-22 11:53 ` Richard Hirst
2001-02-22 11:34 ` Alan Modra
2001-02-22 11:52 ` Richard Hirst
2001-02-22 12:27 ` Alan Modra
2001-02-22 13:03 ` Richard Hirst
2001-02-22 13:27 ` Alan Modra
2001-02-22 17:00 ` Richard Hirst
2001-02-22 17:44 ` Paul Bame
2001-02-23 12:25 ` Richard Hirst
2001-02-23 12:43 ` Alan Modra
[not found] <20010223113052.G4660@linuxcare.com>
[not found] ` <Pine.LNX.4.21.0102232231470.9345-100000@front.linuxcare.com.au>
2001-02-23 21:23 ` Richard Hirst
2001-02-26 17:57 ` Richard Hirst
2001-02-26 21:30 ` Matthew Wilcox
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=d3ofvv57h9.fsf@lxplus015.cern.ch \
--to=jes@linuxcare.com \
--cc=alan@linuxcare.com.au \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.