[issue4358] Segfault in stringobject.c

2009-03-24 Thread STINNER Victor
STINNER Victor victor.stin...@haypocalc.com added the comment: There are not enough informations to reproduce the issue or understand the problem. Since farshad didn't answer since 4 months, I choose to close the bug. Reopen the bug if you have new informations! -- resolution: -

[issue4358] Segfault in stringobject.c

2009-03-17 Thread STINNER Victor
STINNER Victor victor.stin...@haypocalc.com added the comment: farshad: Is the bug still open? If yes, can you give more informations? If you don't answer, I will have to close this issue because it's not possible find the bug with so few informations :-/ --

[issue4358] Segfault in stringobject.c

2008-11-21 Thread STINNER Victor
STINNER Victor [EMAIL PROTECTED] added the comment: The application is a web service with postgresql backend, so it heavily uses pyexpat and pygresql in a threaded environment. pyexpat or pygresql is maybe not thread safe. To catch such error, you have to use Valgrind. And to use Valgrind,

[issue4358] Segfault in stringobject.c

2008-11-19 Thread Farshad Khoshkhui
New submission from Farshad Khoshkhui [EMAIL PROTECTED]: I'm encountering random segfaults on multiple machines. By examining core dumps, it's all happening in stringobject.c (_PyString_Resize or string_join). By using pyframev I figured out it's always happening inside xmlrpclib.py

[issue4358] Segfault in stringobject.c

2008-11-19 Thread Farshad Khoshkhui
Farshad Khoshkhui [EMAIL PROTECTED] added the comment: Another Backtrace. I have three other core dumps with exact same backtrace on two different machines. Added file: http://bugs.python.org/file12064/backtrace2 ___ Python tracker [EMAIL PROTECTED]

[issue4358] Segfault in stringobject.c

2008-11-19 Thread Thomas Heller
Thomas Heller [EMAIL PROTECTED] added the comment: Has nothing to do with ctypes (the package), unassigning. -- components: -ctypes ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4358 ___

[issue4358] Segfault in stringobject.c

2008-11-19 Thread Thomas Heller
Changes by Thomas Heller [EMAIL PROTECTED]: -- assignee: theller - nosy: -theller ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4358 ___ ___

[issue4358] Segfault in stringobject.c

2008-11-19 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: This is difficult: the backtrace only show plain python operations. Some hints though: One backtrace shows a memory corruption in the obmalloc data. This may come from a buffer overrun. You initially selected ctypes in Components,

[issue4358] Segfault in stringobject.c

2008-11-19 Thread Farshad Khoshkhui
Farshad Khoshkhui [EMAIL PROTECTED] added the comment: No, there isn't any custom made C extension, nor I'm using ctypes. (It was a mistake selecting ctypes). The application is a web service with postgresql backend, so it heavily uses pyexpat and pygresql in a threaded environment. I'll