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.

classification
Title: Python Interpreter Crash
Type: crash Stage:
Components: None Versions: Python 2.7, Python 2.6
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: benjamin.peterson, pitrou, quindraco
Priority: normal Keywords:

Created on 2010-08-30 19:08 by quindraco, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
stacktrace.txt quindraco, 2010-08-30 19:08 Output from interpreter crash.
Messages (4)
msg115240 - (view) Author: (quindraco) Date: 2010-08-30 19:08
I am attaching my stacktrace from using Python 2.6, but I get identical behaviour in 2.7.  I suspect that at least one of the underlying modules I'm using is broken, but the interpreter shouldn't crash just because an external module is broken, so I'm reporting the issue.  That's what's happening - I'm crashing the python interpreter.  Here's what I type to cause the issue; I'm not sure what more information is needed.

from django.test.client import Client
c = Client()
response = c.post(logindir, loginvars)
response = c.get(getdir)
msg115245 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-08-30 21:39
This seems to be a pyodbc problem, you should post the issue to them.
When an extension module written in C (pyodbc.so) has an issue, there's nothing Python can do to prevent it from crashing the whole process, since C is an insecure language.
msg115247 - (view) Author: (quindraco) Date: 2010-08-30 22:23
I thought as much, so I've already posted on the pyodbc bug tracker, but thanks for the second opinion; I wasn't sure.  

I realise modules written in C can't be prevented from crashing, but is it really impossible to keep the interpreter from going down with the module?  Surely some sort of sandbox could be put up.
msg115248 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2010-08-30 22:25
Well, that's a another issue completely.
History
Date User Action Args
2022-04-11 14:57:05adminsetgithub: 53927
2010-08-30 22:25:21benjamin.petersonsetstatus: open -> closed
nosy: + benjamin.peterson
messages: + msg115248

2010-08-30 22:23:20quindracosetstatus: pending -> open

messages: + msg115247
2010-08-30 21:39:49pitrousetstatus: open -> pending

nosy: + pitrou
messages: + msg115245

resolution: not a bug
2010-08-30 19:08:55quindracocreate