Re: [BUG] 2.6.22-rc4: wait4() waiting for SIGSTOP may not return if the target process is ptraced

Hi,

At Thu,  7 Jun 2007 02:54:32 -0700 (PDT),
Roland McGrath wrote:
> 
> The bug is in strace (and is being fixed).  It needs to use tgkill instead
> of kill to send that SIGSTOP to the right thread only.  

You mean kill() to specifig thread is fundamentally wrong? If so, current
kill() is wrong because it can receive pid of non main thread.

Thanks,

Satoru
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [BUG] 2.6.22-rc4: wait4() waiting for SIGSTOP may not return if the target process is ptraced
  - From: Roland McGrath <[email protected]>

References:
- Re: [BUG] 2.6.22-rc4: wait4() waiting for SIGSTOP may not return if the target process is ptraced
  - From: Roland McGrath <[email protected]>

Prev by Date: Re: [RFC] PPS: Implementing LinuxPPS API with new syscalls
Next by Date: Re: [PATCH] ahci: Add MCP73/MCP77 support to AHCI driver
Previous by thread: Re: [BUG] 2.6.22-rc4: wait4() waiting for SIGSTOP may not return if the target process is ptraced
Next by thread: Re: [BUG] 2.6.22-rc4: wait4() waiting for SIGSTOP may not return if the target process is ptraced
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]