[issue2546] Python-2.5.2: crash in visit_decref () at Modules/gcmodule.c:270

2008-04-05 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: The crash is because of an error in your C code: in backend.c:: void backend(char *output_filename) { C2py(backend, 1, output_filename); } But your C2py function expects a variable number of PyObject*. I found this

[issue2546] Python-2.5.2: crash in visit_decref () at Modules/gcmodule.c:270

2008-04-05 Thread George Verbitsky
George Verbitsky [EMAIL PROTECTED] added the comment: Thank you, Amaury, very much for helping me with this one. George Amaury Forgeot d'Arc [EMAIL PROTECTED] wrote: Amaury Forgeot d'Arc added the comment: The crash is because of an error in your C code: in backend.c:: void backend(char

[issue2546] Python-2.5.2: crash in visit_decref () at Modules/gcmodule.c:270

2008-04-04 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: Without a single hint about the code your are running, no investigation is possible. And since the traceback shows that the python interpreter is embedded in another application, it could very well be an error in your C code. Please

[issue2546] Python-2.5.2: crash in visit_decref () at Modules/gcmodule.c:270

2008-04-04 Thread Neal Norwitz
Neal Norwitz [EMAIL PROTECTED] added the comment: I'm setting the priority to release blocker for now. George, please provide a way for us to reproduce with a stock python (ie, no third party extensions). Thanks. -- nosy: +nnorwitz priority: - release blocker

[issue2546] Python-2.5.2: crash in visit_decref () at Modules/gcmodule.c:270

2008-04-03 Thread George Verbitsky
New submission from George Verbitsky [EMAIL PROTECTED]: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208408368 (LWP 2816)] 0x080edccd in visit_decref (op=0xbf9289ff, data=0x0) at Modules/gcmodule.c:270 270 if (PyObject_IS_GC(op)) { (gdb) bt #0