New submission from Stan :
Checking if thread.is_alive() while thread is checking on Process.is_alive()
seemingly causes undefined behavior.
The attached POC is expected to print "ThreadN.data == 1999" for N in range(0,
20) with some repeats. However the integers are spread al
Stan Cox added the comment:
The patch works for systemtap except for one minor nit. pydtrace.h, created by
stap from pydtrace.d, is stap specific. Could pydtrace.h not be included in
/Include so that it is always created at build time in
/Include? If PyEval_GetFrame() were passed via
Stan Cox added the comment:
systemtap doesn't have have a ustack helper, but if the frame pointer were
provided to PYTHON_FUNCTION_ENTRY, then it could be cached to provide python
stack frame access.
--- Python/ceval.c.12011-12-07 11:18:03.733659382 -0500
+++ Python/ceval.c 20
stan mihai added the comment:
Disabling optimizations doesn't really fix the issue, just hides it, for now.
The problem was an uninitialized variable. Attached is the patch that fixes it.
--
nosy: +stan.mihai
Added file: http://bugs.python.org/file20527/ctypes_win64
stan mihai added the comment:
Disabling optimizations doesn't really fix the issue, just hides it, for now.
The problem was an uninitialized variable. Attached is the patch that fixes it.
--
keywords: +patch
nosy: +stan.mihai
Added file: http://bugs.python.org/file20528/ctypes_
stan mihai added the comment:
The problem was an uninitialized variable. Attached is the patch that fixes it.
--
keywords: +patch
nosy: +stan.mihai
Added file: http://bugs.python.org/file20529/ctypes_win64.diff
___
Python tracker
<h
stan mihai added the comment:
attached patch with tests
I have no experience with python development so the tests will actually need a
more detailed review. Also I only checked it on win64.
--
Added file: http://bugs.python.org/file20626/ctypes_win64_tests.diff
stan mihai added the comment:
ok, please also fix the first parameter of the tests. Because it has the same
value in the first call and the callback it will always be right by accident,
since the first call puts the value in both standard and floating point
registers
New submission from Stan Hendryx :
The backspace character \b is not processed correctly in IDLE 3.8.2:
>>> print("deleted\b file")
deleted file
Running the interpreter from Terminal, it works:
>>> print("deleted\b file")
delete file
Same result o
Stan Hendryx added the comment:
Hello Terry,
Thank you for your reply. I understand there are different interpretations of
\b. IMHO, since IDLE is part of a python distribution, IDLE needs to be
consistent with the native python interpreter on each platform. On Mac, IDLE
gives
>>&
Stan Cox added the comment:
This is a subset of the dtrace patch and consists of the minimal functionality
needed by systemtap. The only files that are changed from upstream sources are
as follows.
* configure/configure.in
* Makefile.pre.in
* pyconfig.h.in
Same changes as the dtrace patch
Stan Seibert added the comment:
FYI: This bug still exists using the version of clang shipped with OS X 10.8.
Tested with Python 3.3.0b2 and:
Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin12.0.0
Thread model: posix
--
nosy
Stan Seibert added the comment:
I can also confirm that the patch applied to the current tip (663de4dbb88a)
passes test_ctypes now with Clang 4.0 on OS X 10.8.
--
___
Python tracker
<http://bugs.python.org/issue13
Changes by Stan Seibert :
--
nosy: +Stan.Seibert
___
Python tracker
<http://bugs.python.org/issue8713>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Stan Klein :
I got the following traceback on an "import os" statement:
Traceback (most recent call last):
File "setup.py", line 53, in ?
import traceback
File "/usr/lib/python2.6/traceback.py", line 3, in ?
import lineca
15 matches
Mail list logo
