[ python-Bugs-1495033 ] int/long assume that the buffer ends in \0 => CRASH

[SourceForge.net]

Bugs item #1495033, was opened at 2006-05-25 11:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
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: Open
Resolution: None
Priority: 5
Submitted By: James Y Knight (foom)
Assigned to: Nobody/Anonymous (nobody)
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.

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

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