[Python-bugs-list] [ python-Bugs-494203 ] Interpreter won't always exit with daemonic thread

noreply@sourceforge.net noreply@sourceforge.net
Tue, 12 Nov 2002 07:45:43 -0800


Bugs item #494203, was opened at 2001-12-17 14:37
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=494203&group_id=5470

Category: Threads
Group: Python 2.1.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Morten W. Petersen (morphex)
Assigned to: Nobody/Anonymous (nobody)
Summary: Interpreter won't always exit with daemonic thread

Initial Comment:
See file.

----------------------------------------------------------------------

>Comment By: Gustavo Niemeyer (niemeyer)
Date: 2002-11-12 15:45

Message:
Logged In: YES 
user_id=7887

I couldn't reproduce it on Conectiva Linux 8.0 as well.

Looking trough the trace, I found out that there's some
realtime management going on. Then, I tried to preload
librt.so, and that made my trace look pretty similar to the
attached one. Even then, I wasn't able to reproduce the problem.

Morten, can you still reproduce this bug in Python 2.2.2? If
so, I'll look for an environment similar to yours.


----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-12-17 17:06

Message:
Logged In: YES 
user_id=6380

gdb?

----------------------------------------------------------------------

Comment By: Morten W. Petersen (morphex)
Date: 2001-12-17 16:57

Message:
Logged In: YES 
user_id=68005

I can't interpret it either.  :-)

Is there another way to to provide debugging information ?

----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-12-17 16:48

Message:
Logged In: YES 
user_id=6380

Sorry, I don't know how to interpret the trace. Someone
else, please?


----------------------------------------------------------------------

Comment By: Morten W. Petersen (morphex)
Date: 2001-12-17 16:42

Message:
Logged In: YES 
user_id=68005

I'm attaching a trace..

----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-12-17 16:33

Message:
Logged In: YES 
user_id=6380

I dunno. They're likely to shoot back to Python. Can you do
some more digging (e.g. what is the program doing when it's
hanging)?


----------------------------------------------------------------------

Comment By: Morten W. Petersen (morphex)
Date: 2001-12-17 16:21

Message:
Logged In: YES 
user_id=68005

Ok, the system I'm using is:

morten@debian$ python
Python 2.1.1 (#1, Nov 11 2001, 18:19:24) 
[GCC 2.95.4 20011006 (Debian prerelease)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> 
morten@debian$ uname -a
Linux debian 2.4.14 #1 SMP Mon Dec 10 20:40:22 CET 2001 i686
unknown

With a customized kernel.  Should I contact the Debian
maintainers ?

----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-12-17 15:58

Message:
Logged In: YES 
user_id=6380

I can't reproduce this on Red Hat 6.2.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=494203&group_id=5470