RetroSearch Browse

Tue Jul 7 10:10:09 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/140667.html

On 07.07.15 10:42, Serhiy Storchaka wrote:
> On 07.07.15 05:03, raymond.hettinger wrote:
>> https://hg.python.org/cpython/rev/c9782a9ac031
>> changeset:   96865:c9782a9ac031
>> user:        Raymond Hettinger <python at rcn.com>
>> date:        Mon Jul 06 19:03:01 2015 -0700
>> summary:
>>    Tighten-up code in the set iterator to use an entry pointer rather
>> than indexing.

> What if so->table was reallocated during the iteration, but so->used is
> left the same? This change looks unsafe to me.

There is crash reproducer.

http://bugs.python.org/issue24581

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/140667.html below:

[Python-Dev] cpython: Tighten-up code in the set iterator to use an entry pointer rather than