From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: vic <zandy@cs.wisc.edu>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] ptrace on stopped processes (2.4)
Date: Sat, 22 Dec 2001 12:56:01 +0900 [thread overview]
Message-ID: <87adwblxgu.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <m3adwc9woz.fsf@localhost.localdomain>
In-Reply-To: <m3adwc9woz.fsf@localhost.localdomain>
vic <zandy@cs.wisc.edu> writes:
> --- linux-2.4.16/kernel/ptrace.c Wed Nov 21 16:43:01 2001
> +++ linux-2.4.16.1/kernel/ptrace.c Fri Dec 21 10:42:44 2001
> @@ -89,8 +89,10 @@
> SET_LINKS(task);
> }
> write_unlock_irq(&tasklist_lock);
> -
> - send_sig(SIGSTOP, task, 1);
> + if (task->state != TASK_STOPPED)
> + send_sig(SIGSTOP, task, 1);
> + else
> + task->exit_code = SIGSTOP;
> return 0;
>
> bad:
It seems that trace is started in the place different from
usual. Then, I think PTRACE_KILL doesn't work.
If it need, I think it should wake up a task.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2001-12-22 3:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 19:53 [PATCH] ptrace on stopped processes (2.4) vic
2001-12-21 23:19 ` Jeff Dike
2001-12-22 3:56 ` OGAWA Hirofumi [this message]
2001-12-22 17:38 ` Mike Coleman
2002-01-17 16:57 ` vic
2002-01-17 19:23 ` OGAWA Hirofumi
2002-01-23 17:58 ` vic
2002-01-23 22:14 ` OGAWA Hirofumi
2002-01-23 22:29 ` vic
2002-01-24 1:41 ` OGAWA Hirofumi
2002-01-21 3:09 ` Mike Coleman
2002-01-28 20:15 ` vic
2002-03-19 3:59 ` vic
-- strict thread matches above, loose matches on Subject: below --
2003-03-17 21:24 Rajesh Rajamani
2003-03-24 4:09 ` Daniel Jacobowitz
2003-03-24 6:24 ` raj
2003-03-24 15:05 ` Daniel Jacobowitz
2003-03-25 13:48 ` Werner Almesberger
2003-03-25 13:58 ` Daniel Jacobowitz
2003-03-25 14:53 ` Werner Almesberger
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=87adwblxgu.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.com \
--cc=zandy@cs.wisc.edu \
/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.