This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pconnell
Recipients benjamin.peterson, isoschiz, pconnell
Date 2013-07-27.00:01:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1374883307.06.0.100928488796.issue18565@psf.upfronthosting.co.za>
In-reply-to
Content
This is a testcase for issue17669 - it passes against the latest default (and hits the same segfault under 3.3.0).


I came up with this while tracking down a thorny generator finalisation crash that turned out to be a variant on 17669.

The root cause was gen_close being called on a generator that's delegating to another, and whose frame has already had frame_clear called (so f_stacktop is NULL).

It's reproduced by creating a reference cycle that's broken by clearing the delegating generator's frame.
History
Date User Action Args
2013-07-27 00:01:47pconnellsetrecipients: + pconnell, benjamin.peterson, isoschiz
2013-07-27 00:01:47pconnellsetmessageid: <1374883307.06.0.100928488796.issue18565@psf.upfronthosting.co.za>
2013-07-27 00:01:46pconnelllinkissue18565 messages
2013-07-27 00:01:46pconnellcreate