So this was shot down by Alan Cox in the LKML thread I linked to and
since Jean-Paul hasn't made any attempt to convince the people on LKML
otherwise there is no reason to keep this open any longer. Any kind of
change would have to happen upstream and nothing should be special cased
for Ubuntu. If
I took this question to the linux kernel mailing list with Jean-Paul
CC'ed and I think you guys should take discussion there and close this
bug appropriately afterwards. See http://lkml.org/lkml/2009/5/21/275.
--
kill(2) succeeds when no process corresponds to the given PID
https://bugs.launchpad
Hi Simon,
I'm no expert in interpreting POSIX. A casual (but careful) reading of
POSIX 1003.1-2004 suggests that this isn't the intended behavior. It is
implied in a few places, most notably the getpid[1] documentation, that
a process has only one PID (by use of the definite article when
referri
Jean-Paul and Glyph,
by which standard or documentation do you believe the current behaviour
is incorrect? My guess is that the behaviour is completely intentional,
but if documentation says otherwise or can be clarified I'm sure we can
work something out.
--
kill(2) succeeds when no process cor
** Package changed: python-defaults (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
kill(2) succeeds when no process corresponds to the given PID
https://bugs.launchpad.net/bugs/341239
You received this bug notification because you are a member of Ubu
In case anyone still doubts that this is a kernel (or libc) issue, and
thinks it's a Python issue, here's a similar program in C. Note that
this dies even though we are killing an internal thread ID and not the
process's PID.
#include
#include
#include
#include
#define REASONABLE 1024
void
Here's a simple command which can be used to try to reproduce this
behavior (so you don't have to type out the statements in that session
by hand):
python -c '
import os, threading, time
threading.Thread(target=time.sleep, args=(600,)).start()
tids = os.listdir("/proc/" + str(os.getpid()) + "/task
> I've been unable to recreate this in Hardy, Intrepid or Jaunty.
Brian, I wonder what other software might be involved in this behavior.
Is there anything else the version of which I should report?
--
kill(2) succeeds when no process corresponds to the given PID
https://bugs.launchpad.net/bugs/
The previous comment doesn't seem to contain a correct attempt to
reproduce the originally reported problem. Creating a thread and
looking up its task id is a critical step in reproducing the issue. The
bug manifests when sending a signal to a task id.
Also, I don't think this is a Python bug.
(This guy had a python bug - not bash - packaged changed).
In Jaunty this seems to work fine for me:
d...@davros:~$ python
Python 2.6.1+ (r261:67515, Mar 27 2009, 10:52:49)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import os, threading, time
I can reproduce it on hardy
--
kill(2) succeeds when no process corresponds to the given PID
https://bugs.launchpad.net/bugs/341239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've been unable to recreate this in Hardy, Intrepid or Jaunty. In all
three releases I receive an error like so:
-bash: kill: (6312) - No such process
** Changed in: bash (Ubuntu)
Sourcepackagename: None => bash
--
kill(2) succeeds when no process corresponds to the given PID
https://bugs.lau
** Summary changed:
- in kvm guest, kill(2) succeeds when no process corresponds to the given PID
+ kill(2) succeeds when no process corresponds to the given PID
** Description changed:
- Binary package hint: kvm
+ The kill(2) call behaves incorrectly. Here is an example Python session
+ which
13 matches
Mail list logo
