From: Badari Pulavarty <pbadari@gmail.com>
To: Bernhard Rosenkraenzer <bero@arklinux.org>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: 2.6.15-rc1-mm2 breaks strace
Date: Fri, 18 Nov 2005 15:00:35 -0800 [thread overview]
Message-ID: <1132354835.24066.195.camel@localhost.localdomain> (raw)
In-Reply-To: <200511182240.34512.bero@arklinux.org>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
On Fri, 2005-11-18 at 22:40 +0100, Bernhard Rosenkraenzer wrote:
> 2.6.15-rc1-mm2 works nicely here, aside from the artsd stuff someone else
> already reported, and an new issue with strace (last known working:
> 2.6.14-mm2)
>
> [bero@localhost bero]$ strace ls
> execve("/bin/ls", ["ls"], [/* 33 vars */]) = 0
> Segmentation fault
> [ls output without any traces beyond execve-ing ls displayed here]
>
> Also interesting:
> [bero@localhost bero]$ strace strace ls
> execve("/usr/bin/strace", ["strace", "ls"], [/* 20 vars */]) = 0
> Segmentation fault
> execve("/bin/ls", ["ls"], [/* 20 vars */]) = 0
> [ls output without any traces displayed here]
Try Christoph's patch.
Thanks,
Badari
[-- Attachment #2: ptrace-fix.patch --]
[-- Type: text/x-patch, Size: 554 bytes --]
Looks like 2.6.15-rc1-mm1 has total crap in ptrace_get_task_struct
(and it looks like my fault because I sent out a wrong patch).
The patch below should fix it:
Index: linux-2.6/kernel/ptrace.c
===================================================================
--- linux-2.6.orig/kernel/ptrace.c 2005-11-18 10:25:35.000000000 +0100
+++ linux-2.6/kernel/ptrace.c 2005-11-18 10:25:54.000000000 +0100
@@ -459,7 +459,7 @@
read_unlock(&tasklist_lock);
if (!child)
return ERR_PTR(-ESRCH);
- return 0;
+ return child;
}
#ifndef __ARCH_SYS_PTRACE
prev parent reply other threads:[~2005-11-18 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 21:40 2.6.15-rc1-mm2 breaks strace Bernhard Rosenkraenzer
2005-11-18 22:37 ` Jiri Slaby
2005-11-18 23:00 ` Badari Pulavarty [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=1132354835.24066.195.camel@localhost.localdomain \
--to=pbadari@gmail.com \
--cc=akpm@osdl.org \
--cc=bero@arklinux.org \
--cc=linux-kernel@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 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.