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 xdegaye
Recipients benjamin.peterson, jcea, xdegaye
Date 2013-03-01.11:29:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362137349.08.0.649996532446.issue17288@psf.upfronthosting.co.za>
In-reply-to
Content
Nosying Benjamin Peterson who knows frame_setlineno (issue 14612) and nosying
Jesús Cea Avión. Hoping they don't mind.

This problem occurs also when setting f_lineno from an exception debug event.

One may crash the interpreter (or get a "SystemError: unknown opcode") when the
return debug event is one that handles a yield statement.  For example the
following test causes a segmentation fault on python 3.3.0:

$ python /tmp/jump.py
> /tmp/jump.py(7)<module>()
-> for i in gen():
(Pdb) step
--Call--
> /tmp/jump.py(1)gen()
-> def gen():
(Pdb) step
> /tmp/jump.py(2)gen()
-> for i in range(1):
(Pdb) step
> /tmp/jump.py(3)gen()
-> yield i
(Pdb) step
--Return--
> /tmp/jump.py(3)gen()->0
-> yield i
(Pdb) jump 2
> /tmp/jump.py(2)gen()->0
-> for i in range(1):
(Pdb) step
> /tmp/jump.py(8)<module>()
-> lineno = 8
(Pdb) step
> /tmp/jump.py(7)<module>()
-> for i in gen():
(Pdb) step
--Call--
> /tmp/jump.py(2)gen()->0
-> for i in range(1):
(Pdb) step
Segmentation fault
History
Date User Action Args
2013-03-01 11:29:09xdegayesetrecipients: + xdegaye, jcea, benjamin.peterson
2013-03-01 11:29:09xdegayesetmessageid: <1362137349.08.0.649996532446.issue17288@psf.upfronthosting.co.za>
2013-03-01 11:29:09xdegayelinkissue17288 messages
2013-03-01 11:29:08xdegayecreate