public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ptrace problem in 2.6.9
Date: Mon, 25 Oct 2004 07:51:37 +0000	[thread overview]
Message-ID: <16764.45193.900066.555108@napali.hpl.hp.com> (raw)
In-Reply-To: <20041022170557.GW19372@frankl.hpl.hp.com>

>>>>> On Sat, 23 Oct 2004 01:25:42 -0700, David Mosberger <davidm@linux.hpl.hp.com> said:

>>>>> On Fri, 22 Oct 2004 10:05:57 -0700, Stephane Eranian <eranian@hpl.hp.com> said:
  Stephane> Hi Roland, I have some problems with the recent
  Stephane> modifications to the Ptrace infrastructure in 2.6.9
  Stephane> release. Basically I have the smiple test program attached
  Stephane> to this E-mail and it hangs in 2.6.9 but not in
  Stephane> 2.6.9-rc4. Somehow the first waitpid() does not return. It
  Stephane> is not clear to me why.  Is there something Ineed to
  Stephane> change in the call itself?  I am running all of this on a
  Stephane> 2-way IA-64 machine with 2.6.9. I have not tried on x86.

  David> Shoot, I think I ran into the same problem yesterday when
  David> running the GCC testsuite.  In my case, the problem seemed to
  David> disappear (mostly) after downgrading "expect" from the
  David> "unstable" to the "stable" version, but the symptoms where
  David> exactly like in your case: waitpid() didn't return, so I
  David> suspect it really was the kernel's fault.  I'll try Roland's
  David> patch on Monday.

Then again, may be not: it appears that the bug only relates to
PTRACE'd processes, which "expect" is unlikely to do.  Oh, well, would
have been too easy.

	--david

  parent reply	other threads:[~2004-10-25  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 17:05 ptrace problem in 2.6.9 Stephane Eranian
2004-10-23  4:53 ` Roland McGrath
2004-10-23  8:25 ` David Mosberger
2004-10-25  7:51 ` David Mosberger [this message]
2004-10-25  8:04 ` Stephane Eranian

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=16764.45193.900066.555108@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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