[ python-Bugs-971213 ] another threads+readline+signals nasty

[SourceForge.net]

Bugs item #971213, was opened at 2004-06-11 15:30
Message generated for change (Comment added) made by gbrandl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=971213&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: None
Status: Open
Resolution: Works For Me
Priority: 7
Submitted By: Anthony Baxter (anthonybaxter)
Assigned to: Anthony Baxter (anthonybaxter)
Summary: another threads+readline+signals nasty

Initial Comment:
python -c "import time, readline, thread;
thread.start_new_thread(raw_input, ()); time.sleep(2)"

Segfaults on ^C<return>

Fails on Linux, freebsd.

On linux (FC - using kernel 2.6.1, glibc 2.3.3, gcc-3.3.3)

(gdb) where
#0  0x002627a2 in _dl_sysinfo_int80 () from
/lib/ld-linux.so.2
#1  0x008172b1 in ___newselect_nocancel () from
/lib/tls/libc.so.6
#2  0x0011280b in time_sleep (self=0x0, args=0xb7fe17ac)
    at Modules/timemodule.c:815

on FreeBSD 5.2.1-RC, a different error.

Fatal error 'longjmp()ing between thread contexts is
undefined by POSIX 1003.1' at line 72 in file
/usr/src/lib/libc_r/uthread/uthread_jmp.c (errno = 2)
Abort (core dumped)


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

>Comment By: Georg Brandl (gbrandl)
Date: 2006-08-19 05:35

Message:
Logged In: YES 
user_id=849994

Not reproducable here either (Gentoo x86).

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

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-08-19 03:09

Message:
Logged In: YES 
user_id=33168

This doesn't crash for me any more.  I remember there was
another fix for socket timeouts and Ctrl-C.  Maybe that
fixed this too?  Anthony, can you reproduce this?

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

Comment By: Michael Hudson (mwh)
Date: 2005-10-03 11:13

Message:
Logged In: YES 
user_id=6656

I can't, on OS X or debian.  

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

Comment By: Neal Norwitz (nnorwitz)
Date: 2005-10-03 04:12

Message:
Logged In: YES 
user_id=33168

I can reproduce with cvs head (gentoo linux/amd64).

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

Comment By: Michael Hudson (mwh)
Date: 2005-04-07 09:03

Message:
Logged In: YES 
user_id=6656

I think this is fixed now, as in I can't reproduce it with CVS 
HEAD. Not sure why!  I can think of a few fixes that might be responsible.

It still messes the terminal up, though.

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

Comment By: Michael Hudson (mwh)
Date: 2004-08-07 21:41

Message:
Logged In: YES 
user_id=6656

Bah, this still segfaults with CVS head.

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

Comment By: Michael Hudson (mwh)
Date: 2004-06-21 10:45

Message:
Logged In: YES 
user_id=6656

Can you try the patch that's *now* in 960406?  It seems to help 
for me (but I really would rather not think too hard about this!).

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

Comment By: Michal Pasternak (mpasternak)
Date: 2004-06-11 15:43

Message:
Logged In: YES 
user_id=799039

readline used on FreeBSD was readline-4.3pl5; everything else: gcc 3.3.3, 
ncurses, libc were standard from 5.2.1.

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

Comment By: Anthony Baxter (anthonybaxter)
Date: 2004-06-11 15:39

Message:
Logged In: YES 
user_id=29957

The patch in #960406 doesn't help here.

The FC test system also has readline-4.3, if it helps, as
does the FreeBSD box. It apparently doesn't crash on OSX.



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

Comment By: Michael Hudson (mwh)
Date: 2004-06-11 15:38

Message:
Logged In: YES 
user_id=6656

Hmm.  Doesn't crash on OS X.  Messes the terminal up good and 
proper, though.

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

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