Bugs item #909295, was opened at 2004-03-03 14:53
Message generated for change (Comment added) made by tim_one
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=909295&group_id=5470
Category: Python Interpreter Core
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Chuck Mason (cemason)
Assigned to: Nobody/Anonymous (nobody)
Summary: segmentation fault
Initial Comment:
$ python
Python 2.3.1 (#1, Sep 23 2003, 10:07:41)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2
Type "help", "copyright", "credits" or "license" for
more information.
def func(*a): print a
...
func((1, 2, 3)
... )Segmentation fault
--------------------------
Not sure what other information you need, but I tested
it on several machines with the same version and it
seems to be hardware/other library independant.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2004-03-04 09:59
Message:
Logged In: YES
user_id=31435
Get into a debugger and show the top dozen functions on the
call stack when the segfault occurs. Segfaults in an
interactive shell unique to Unixish systems usually get pinned
on GNU readline in the end.
----------------------------------------------------------------------
Comment By: Jarek Zgoda (zgoda)
Date: 2004-03-04 03:59
Message:
Logged In: YES
user_id=92222
No such weirdness on W2KSp4 with Python 2.3.2
----------------------------------------------------------------------
Comment By: Raymond Hettinger (rhettinger)
Date: 2004-03-03 23:05
Message:
Logged In: YES
user_id=80475
On WinMe, I cannot reproduce this on Py2.2.3, Py2.3.3, or
Py2.4a0.
----------------------------------------------------------------------