#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
-----------------------------------+------------------------------------
Reporter: stevejalim | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: master
Severity: Normal | Resolution:
Keywords: sqlite nose | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by pieterdd):
As far as I can tell, all the fixes in this thread are workarounds that -
at least temporarily - keep the segmentation fault from manifesting itself
while not addressing the root cause.
Now, I don't have a solution myself. But I just want to point out that
creating a dummy boolean value to trigger a subtle change in the way
memory is allocated does not guarantee that the bug won't be triggered
again and that it does nothing to address the underlying issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/24080#comment:49>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.8f086019bf87d598a40f8ed9bba95e96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
