int/long assume that the buffer ends in \0 => CRASH

[foom]

BPO	1495033
Nosy	@brettcannon

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/brettcannon'
closed_at = <Date 2006-06-08.17:02:12.000>
created_at = <Date 2006-05-25.15:51:31.000>
labels = ['interpreter-core']
title = 'int/long assume that the buffer ends in \\0 => CRASH'
updated_at = <Date 2006-06-08.17:02:12.000>
user = 'https://bugs.python.org/foom'

bugs.python.org fields:

activity = <Date 2006-06-08.17:02:12.000>
actor = 'brett.cannon'
assignee = 'brett.cannon'
closed = True
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2006-05-25.15:51:31.000>
creator = 'foom'
dependencies = []
files = []
hgrepos = []
issue_num = 1495033
keywords = []
message_count = 3.0
messages = ['28640', '28641', '28642']
nosy_count = 3.0
nosy_names = ['nnorwitz', 'brett.cannon', 'foom']
pr_nums = []
priority = 'high'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1495033'
versions = []

[foom]

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.

[nnorwitz]

Logged In: YES
user_id=33168

Brett, here's an easy one for ya to get started. :-)

[brettcannon]

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.