[issue21975] Using pickled/unpickled sqlite3.Row results in segfault rather than exception

Elizabeth Myers report at bugs.python.org
Mon Jul 14 02:01:29 CEST 2014


New submission from Elizabeth Myers:

Pickling, unpickling, then using an sqlite3.Row object results in a segfault on at least Python 3.3.5, 3.4.0, and 3.4.1. I have attached a test case and a backtrace below.

I know you're not supposed to pickle sqlite3.Row objects, as the given test case below results in an exception to the effect that sqlite3.Row objects cannot be pickled in Python 2.7. I don't think a segfault is the desired behaviour, however...

----------
components: Library (Lib)
files: testcase.py
messages: 222982
nosy: Elizacat
priority: normal
severity: normal
status: open
title: Using pickled/unpickled sqlite3.Row results in segfault rather than exception
type: crash
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file35947/testcase.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21975>
_______________________________________


More information about the Python-bugs-list mailing list