Bugs item #1495033, was opened at 2006-05-25 08:51
Message generated for change (Comment added) made by bcannon
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1495033&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: Closed
>Resolution: Fixed
Priority: 7
Submitted By: James Y Knight (foom)
Assigned to: Brett Cannon (bcannon)
Summary: int/long assume that the buffer ends in \0 => CRASH
Initial Comment:
But it doesn't, always.
>>> int(buffer('123a', 0, 3))
Traceback (most recent call last):
File "<stdin>", line 1, in ?
ValueError: invalid literal for int(): 123a
Hmmmmmm...well if that works, how about this one:
>>> import array; int(buffer(array.array('c', [])))
***SEGFAULT***
Ah, there we go, a nice crasher.
----------------------------------------------------------------------
>Comment By: Brett Cannon (bcannon)
Date: 2006-06-08 10:02
Message:
Logged In: YES
user_id=357491
Rev. 46757 has the fix for 2.5 . Not backporting since it
is a big semantic change and the bug doesn't really cause
issues usually.
----------------------------------------------------------------------
Comment By: Neal Norwitz (nnorwitz)
Date: 2006-05-26 00:02
Message:
Logged In: YES
user_id=33168
Brett, here's an easy one for ya to get started. :-)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1495033&group_id=5470
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
