[issue3661] sys.call_tracing segfaults

2008-10-16 Thread Barry A. Warsaw
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: r66949 -- resolution: -> accepted status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3661] sys.call_tracing segfaults

2008-10-04 Thread Benjamin Peterson
Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Attaching patch. -- keywords: +needs review, patch Added file: http://bugs.python.org/file11702/fix_call_tracing_segfault.patch ___ Python tracker <[EMAIL PROTECTED]>

[issue3661] sys.call_tracing segfaults

2008-10-02 Thread Barry A. Warsaw
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3661] sys.call_tracing segfaults

2008-09-26 Thread Barry A. Warsaw
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3661] sys.call_tracing segfaults

2008-09-17 Thread Barry A. Warsaw
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3661] sys.call_tracing segfaults

2008-09-03 Thread Barry A. Warsaw
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: This bug should be fixed for rc2, but it doesn't need to block rc1. -- nosy: +barry priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]>

[issue3661] sys.call_tracing segfaults

2008-08-24 Thread Benjamin Peterson
Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Not applicable in 2.6: Traceback (most recent call last): File "", line 1, in TypeError: type() takes 1 or 3 arguments -- nosy: +benjamin.peterson versions: -Python 2.6 ___ Python tracker <

[issue3661] sys.call_tracing segfaults

2008-08-24 Thread Christian Heimes
Christian Heimes <[EMAIL PROTECTED]> added the comment: The function call fails much earlier in debug builds. sys_call_tracing() doesn't check the type of the second argument. It must be a tuple because it's directly passed to the PyObject_Call() API. Suggestion: Add an explicit type check for P

[issue3661] sys.call_tracing segfaults

2008-08-24 Thread Daniel Diniz
New submission from Daniel Diniz <[EMAIL PROTECTED]>: The following code causes a segfault for me: import sys; sys.call_tracing(type,2) Running on: Python 3.0b3+ (py3k:66015, Aug 24 2008, 16:21:19) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 gdb output: [New Thread -12