devious code can crash structseqs

[mwhudson]

BPO	526039
Nosy	@mwhudson

^{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/mwhudson'
closed_at = <Date 2002-03-06.17:18:42.000>
created_at = <Date 2002-03-05.18:06:22.000>
labels = ['interpreter-core']
title = 'devious code can crash structseqs'
updated_at = <Date 2002-03-06.17:18:42.000>
user = 'https://github.com/mwhudson'

bugs.python.org fields:

activity = <Date 2002-03-06.17:18:42.000>
actor = 'mwh'
assignee = 'mwh'
closed = True
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2002-03-05.18:06:22.000>
creator = 'mwh'
dependencies = []
files = []
hgrepos = []
issue_num = 526039
keywords = []
message_count = 2.0
messages = ['9522', '9523']
nosy_count = 1.0
nosy_names = ['mwh']
pr_nums = []
priority = 'high'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue526039'
versions = ['Python 2.2']

[mwhudson]

Some days you feel that whenever you look closely at
something, you find bugs in it.

>>> import time
>>> class C:
...  def __getitem__(self, i):
...   raise IndexError
...  def __len__(self):
...   return 9
...
>>> time.struct_time(C())
Segmentation fault (core dumped)

This isn't hard to fix (use the PySequence_Fast API),
but I have all sorts of changes in my copy of
Objects/structseq.c and I don't want to forget this.

[mwhudson]

Logged In: YES
user_id=6656

Fixed in revision 1.5 of Objects/structseq.c.
Test in revision 1.3 of Lib/test/test_structseq.py.