From: joshk@triplehelix.org (Joshua Kwan)
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Weirdness with suspending jobs in 2.6.9-rc3
Date: Mon, 11 Oct 2004 14:16:05 -0700 [thread overview]
Message-ID: <20041011211605.GD3316@triplehelix.org> (raw)
In-Reply-To: <200410112055.i9BKt5LI031359@magilla.sf.frob.com>
On Mon, Oct 11, 2004 at 01:55:05PM -0700, Roland McGrath wrote:
> That is a clearly bogus argument. (In fact it looks like a stack address,
> a common thing to be found in uninitialized variables.) Unless you have
> some reason to suspect that this is not the argument actually passed by
> make, then you should look at make and see why it passed the bogus
> argument. So far, I still don't see a direct suggestion of a kernel bug
> here.
All I know is that this doesn't happen in kernels where the waitid patch
was not applied. It has *NEVER* happened until now.
Possibly it was strace catching the wrong end of whatever make was doing
when it started ptracing it.
Could it be glibc's problem.
--
Joshua Kwan
next prev parent reply other threads:[~2004-10-11 21:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 6:33 Weirdness with suspending jobs in 2.6.9-rc3 Joshua Kwan
2004-10-09 10:15 ` Adrian Bunk
2004-10-09 14:16 ` Joshua Kwan
2004-10-09 21:05 ` Andrew Morton
2004-10-10 7:39 ` Joshua Kwan
[not found] ` <20041010004524.0bf6d42e.akpm@osdl.org>
2004-10-10 7:55 ` Joshua Kwan
2004-10-10 21:15 ` Joshua Kwan
2004-10-11 20:55 ` Roland McGrath
2004-10-11 21:16 ` Joshua Kwan [this message]
2004-10-11 23:09 ` Roland McGrath
2004-10-12 3:39 ` Petri Kaukasoina
2004-10-12 3:45 ` Andrew Morton
2004-10-12 3:51 ` Petri Kaukasoina
2004-10-12 4:14 ` Andrew Morton
2004-10-12 3:52 ` Andrew Morton
2004-10-12 3:56 ` Petri Kaukasoina
2004-10-12 4:11 ` Petri Kaukasoina
2004-10-11 23:27 ` Andrew Morton
2004-10-11 18:25 ` Adrian Bunk
2004-10-11 18:35 ` Joshua Kwan
2004-10-14 21:51 ` Tomasz Torcz
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=20041011211605.GD3316@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@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