New submission from Xinmeng Xia :
Popen works when stdio fds are available. However, when interrupting popen in a
recursive function call. The Python interpreter reports a Fatal Python error.
test.py
import subprocess
import os
import sys
def
New submission from Xinmeng Xia :
See the following 'test.py', we call client.makepasv() in socket, and then
create_connection. Recursively calling makepasv() finally leads to core dumped.
System: Python 3.10.1, 3.11.0a3 ,master on Ubuntu 18.04
Reproduce step:
1. executing "
Xinmeng Xia added the comment:
A simpler example to reproduce it:
test.py
import threading
import ctypes
from test import test_code
def test_free_different_thread():
f = test_code.CoExtra().get_func()
class ThreadTest(threading.Thread
Change by Xinmeng Xia :
--
title: UnboundLocalError leads to Illegal instruction crashing CPython ->
Mutithread leads to Illegal instruction crashing CPython
___
Python tracker
<https://bugs.python.org/issu
New submission from Xinmeng Xia :
The following code 1 calls function 'compile' and 'exec' and execute a
statement "s=1". Then we print the value of 's'. This code can perform well on
Python 3.9.2 and output the expected result. However, we pack the wh
New submission from Xinmeng Xia :
In following example, we only give 10 arguments to
tarfile.open(). The error message shows "11 arguments were given".We give
it 5 arguments and the error message shows "6 were given".
New submission from Xinmeng Xia :
See the following examples, ctypes.resize is a built-in function and it's
hashable. ctypes.memset is a C function (CFunctionType object) and it's
“unhashable”. However, ctypes.resize and ctypes.memset are both immutable.
They should act t
New submission from Xinmeng Xia :
When the argument of input() is very long text, the interpreter crashes. This
bug can be reproduced Python 3.9.2 and Python 2.7.18 on Ubuntu 3.9.2 with
GCC7.5.0. I try to reproduce this bug on other version of Python and Operating
System, but it fails
Change by Xinmeng Xia :
--
title: nterpreter crashes when handling long text in input() -> interpreter
crashes when handling long text in input()
___
Python tracker
<https://bugs.python.org/issu
New submission from Xinmeng Xia :
At line 12-20, cpython/Misc/README.valgrind, the descriptions are out of date.
File "Objects/obmalloc.c" does not contain Py_USING_MEMORY_DEBUGGER any more
since Python 3.6. The descriptions should be modified for Python 3.6-3.10
Attached
Change by Xinmeng Xia :
--
type: compile error -> enhancement
___
Python tracker
<https://bugs.python.org/issue43509>
___
___
Python-bugs-list mailing list
Un
New submission from Xinmeng Xia :
nis.maps() with long string argument will lead to segfault of interpreter. See
the following example:
=
Python 3.10.0a6 (default, Mar 19 2021, 11:45:56) [GCC 7.5.0] on linux
Type "help",
New submission from Xinmeng Xia :
Setting the first argument of locale.dgettext() long string, Python interpreter
crashes.
==
Python 3.10.0a6 (default, Mar 19 2021, 11:45:56) [GCC 7.5.0] on linux
Type "help", "copyright
New submission from Xinmeng Xia :
Python interpreter will exit when using Ctrl C to interrupt some Python module
functions with read operations. e.g. sndhdr.what(0),
pdb.find_function('abs/'*10,False), mimetypes.read_mime_types(0). This is
not the expected behavior. Ctrl C i
New submission from Xinmeng Xia :
In Ubuntu 16.04, termios.tcflow(1, 0) cannot be interrupted by Ctrl C, Ctrl D,
Ctrl Z.
It work well on mac OS. (Ctrl C can interrupt it on Mac OS).
Reproduce:
1. type 'python3' in command console;
2. type ‘import termios; termios.tcflow(1, 0)’
3.
New submission from Xinmeng Xia :
Python interpreter cannot work well and report errors after interrupting
logging.config.fileConfig()
Reproduce step:
1. type python3 in console
2. type import logging.config; logging.config.fileConfig({2,2,'sdf'},'')
3
New submission from Xinmeng Xia :
Long computations in pdb.run() lead to interpreter crashes.
Crash example
===
Python 3.9.2 (default, Mar 12 2021, 15:08:35)
[GCC 7.5.0] on linux
Type "help", "copyright", "credi
Change by Xinmeng Xia :
--
type: behavior -> enhancement
___
Python tracker
<https://bugs.python.org/issue43549>
___
___
Python-bugs-list mailing list
Un
Xinmeng Xia added the comment:
Attached testing results of gdb and valgrind. (No error is reported for
locale.dgettext('abs'*10,''))
$gdb ./python
(gdb) run
>>> locale.dgettext('abs'*1000,'')
Program received signal SIGSEGV, Segmentatio
Xinmeng Xia added the comment:
pdb.run() seems crashing different positions of Python (Python/ast_opt.c:488
for pdb.run, Python/ast_opt.c:494 for compile()). But the commit
364d0d20f924071b749e5a889eca22628f4892a3, PR 23744, bpo-42609 for compile()
also fix this bug in pdb.run(). Should we
New submission from Xinmeng Xia :
Long paths as arguments of imp.load_dynamic() lead to interpreter crashes.
Crash example
=
Python 3.10.0a2 (default, Nov 24 2020, 14:18:46)
[GCC 7.5.0] on linux
Type "help", "copyright", &
New submission from Xinmeng Xia :
We write a fuzz tool to fuzz Python standard libraries, and find three crashes:
dis.dis(), dis.get_instructions() dis.show_code() in dis module.
dis.dis()
==
xiaxinmeng:~ xiaxinmeng$ python3.10
Python 3.10.0a3
Xinmeng Xia added the comment:
This crash cannot be reproduced again on the master branch of CPython. It
seems that this bug has been fixed. Should we close this issue and mark it as
"fixed"?
--
___
Python tracker
<https://bu
Xinmeng Xia added the comment:
Program like following reports error on CPython(master branch), however this
program can work well on PyPy. I think this is a bug in CPython
==
string ="""
if 1:
print("hello")
"
New submission from Xinmeng Xia :
The following program can trigger segfault on all releases of Python. I think
it may be caused by incorrect arguments.
Version of Python: 3.6 - master(3.11.0a0)
system: ubuntu 16.04
test.py
import select
def
New submission from Xinmeng Xia :
This program can trigger "Aborted (core dumped)" on Python 3.9.0, Python 3.8.0,
Python3.10.0a2. It trigger " segmentation fault" on the master (Python
3.11.0a0).
==
import weakref
class Object:
de
New submission from Xinmeng Xia :
This piece of code is originally from
https://github.com/python/cpython/tree/main/Lib/test/test_weakref.py. In
function test_proxy_iter(), we change the original data dependency and then
this generated test case (see the following "test.py") cras
New submission from Xinmeng Xia :
Normally after executing a piece of code in a function, locals() should contain
the local variables and these variables can be reassigned next. In the
following code, "attr" should be found in locals(). Actually, it can not be
found in either l
New submission from Xinmeng Xia :
The following crashing can only reproduce on Python3.11. In this case, we
import "asyncio" after deleting a coroutine object and before cleaning it up,
leading to crashing.
test.py
===
async def f():
pass
f = f()
frame =
New submission from Xinmeng Xia :
In Python 3.11, unittest.assertRaisesRegex is broken and leading to crashing if
tested regex does not match name. See the following example:
test.py
=
import unittest
class uTest(unittest.TestCase):
pass
uTest
Xinmeng Xia added the comment:
Thanks for testing it. Maybe it only crashes on Unix-like operating systems. I
also try it on MacOS 11.6.1. with -i to ensure that python survives running the
test code. On MacOS, it reports the following crashing information:
---
xxm$ Python
New submission from Xinmeng Xia :
The following code can lead to a crash and report Illegal instruction (core
dumped)(few times) or Trace/breakpoint trap (core dumped) (very few times) or
Segmentation fault (core dumped) (most times) on Python 3.11.
test_free_different_thread.py
New submission from Xinmeng Xia :
This program can work well on Python 3.5.2 and Python2.7 with the following
output.
"Invalid Entry, try again"
However it will crash on Python3.9.0rc1, 3.10.0a2 with the following error
message:
"
Fatal Python error: _Py_CheckRecursiveCall:
New submission from Xinmeng Xia :
The following program 1 can crash in Python 3. We have reproduce it in the
Python version 3.5, 3.6, 3.7, 3.8, 3.9, 3.10. This bug seems to be similar to
issue 36272, however, the tracking system shows issue 36272 has been fixed and
the program 2, which
Xinmeng Xia added the comment:
But program like following program 3 will not cause any core dump,
RecursionError is also being caught in this Recursion.
program 3
def rec():
try:
rec()
except:
pass
rec()
Beside,I use sys.setrecursionlimit(80
New submission from Xinmeng Xia :
Running the following program:
==
def foo():
try:
1/0
except ZeroDivisionError as e:
ZeroDivisionError = 1
foo()
==
The expected output should be nothing. ZeroDivisionError is
Xinmeng Xia added the comment:
Similar bugs exist in other exceptions.
--
___
Python tracker
<https://bugs.python.org/issue42632>
___
___
Python-bugs-list mailin
New submission from Xinmeng Xia :
=
import traceback
def foo():
traceback.print_exc()
foo()
foo()
Try running the above program, the interpreter is crashed with the error
message like the following:
Fatal Python error: Cannot recover from stack
New submission from Xinmeng Xia :
Considering the following two program,running the program 1 will get expected
output: RecursionError
program 1
===
import traceback
def foo():
try:
1/0
except Exception as e
Change by Xinmeng Xia :
--
title: Title: Recursive traceback crashes Python Interpreter -> Recursive
traceback crashes Python Interpreter
___
Python tracker
<https://bugs.python.org/issu
Xinmeng Xia added the comment:
In issue #42500, crashes is resulted by recursion and try-except. Program like
following will crash the interpreter.
=
def foo():
try:
1/0
except:
pass
foo()
foo()
=
However with traceback module
Xinmeng Xia added the comment:
In issue#36272, they discuss a bug in logging module. They show an example
which is similar as this one. So I think I think there might be a similar bug
in traceback module.
--
___
Python tracker
<ht
Xinmeng Xia added the comment:
Thanks for fixing this, looking forward to the new version.
Could you please kindly change the resolution into fixed and close this report?
--
___
Python tracker
<https://bugs.python.org/issue42
Xinmeng Xia added the comment:
Thank you very much, looking forward to the new Python version.
Could you please kindly change the resolution into fixed and close this issue?
--
___
Python tracker
<https://bugs.python.org/issue42
New submission from Xinmeng Xia :
Calling function ast.literal_eval() with large size can cause a segmentation
fault in Python 3.5 -3.10. Please check the following two examples. The example
1 works as expected, while the second one triggers segmentation fault on Python
New submission from Xinmeng Xia :
Calling function eval() with large size can cause a segmentation fault in
Python 3.7 -3.10. Please check the following two examples. The example 1 works
as expected, while the second one triggers segmentation fault on Python
3.7,3.8,3.9,3.10. The primary
New submission from Xinmeng Xia :
Calling function compile() with large size can cause a segmentation fault in
Python 3.7 -3.10. Please check the following two examples. The example 1 works
as expected, while the second one triggers segmentation fault on Python
3.7,3.8,3.9,3.10. The primary
New submission from Xinmeng Xia :
Calling function exec() with large size can cause a segmentation fault in
Python 3.7 -3.10. Please check the following two examples. The example 1 works
as expected, while the second one triggers segmentation fault on Python
3.7,3.8,3.9,3.10. The primary
New submission from Xinmeng Xia :
Calling function ast.parse() with large size can cause a segmentation fault in
Python 3.5 -3.10. Please check the following two examples. The example 1 works
as expected, while the second one triggers segmentation fault on Python
3.5,3.6,3.7,3.8,3.9,3.10
New submission from Xinmeng Xia :
The following program can work well in Python 2. However it crashes in Python
3( 3.6-3.10 ) with the following error messages.
Program:
import sys,time, threading
class test:
def test(self):
pass
Xinmeng Xia added the comment:
Thanks for your kind explanation! Now, I have understand the causes of this
core dump. Considering it will not cause core dump in Python 2.x, I am
wondering should we suggest an exception to catch it rather than "core
New submission from Xinmeng Xia :
In "Python/Lib/test/crashers/README", it said "This directory only contains
tests for outstanding bugs that cause the
interpreter to segfault. Once the crash is fixed, the test case should be
moved into an appropriate test."
The fil
New submission from Xinmeng Xia :
In "Python/Lib/test/crashers/", only tests for outstanding bugs that cause the
interpreter to segfault should be included.
The file "trace_at_recursion_limit.py" has been fixed on Python 3.7, 3.8, 3.9,
3.10. No segmentation fault will b
Change by Xinmeng Xia :
--
type: enhancement -> behavior
___
Python tracker
<https://bugs.python.org/issue42735>
___
___
Python-bugs-list mailing list
Un
Xinmeng Xia added the comment:
Yes，you are right. I thought it was fixed,but it wasn't. Thanks.
--
type: enhancement -> behavior
___
Python tracker
<https://bugs.python.org
New submission from Xinmeng Xia :
Let's see the following program:
def foo():
try:
yield
except:
yield from foo()
for m in foo():
print(i)
===
Expected output:
On line"print(i)", NameError:
New submission from Xinmeng Xia :
This program is initially from
"cpython/Lib/test/crashers/warnings_del_crasher.py" in Python 2.7. The original
case is fixed for all version of Python and removed from "crashers" directory.
However, if we replace the statement &quo
Xinmeng Xia added the comment:
Thanks for your kind explanation! My description is a little confusing. Sorry
about that. The problem here is that the program should stop when the exception
is caught whatever the exception is. (I think bpo-25612 (#1773) fixed exception
selection problems and
Xinmeng Xia added the comment:
Thank you, but I don't think this is a duplicate of issue42717. This crash is
probably caused by the parameter "target" of Thread. "Target" accept the
"callable object". Defaults to None. In this program, it's assigned to
Xinmeng Xia added the comment:
Could we try to limit the number of thread or state or something? I mean if we
set parameter of "range", for example, to 1000 or less here, the crash will no
longer happen. I think the parser can not handle too heavy loop so that i
Xinmeng Xia added the comment:
Thank you for your patient reply. I see now. Hoping that some one can figure
out a good idea to fix this problem.
--
___
Python tracker
<https://bugs.python.org/issue42
Xinmeng Xia added the comment:
Now I see. By the way, I think this case should be moved back to
"cpython/Lib/test/crashers/" since the bug still exists. It is not fixed
completely, the old case is outdated. I suggest we can put the new case into
directory
New submission from Xinmeng Xia :
Running the following program will lead to an unexpected EOF error. If we
delete the space before triple-quotation mark("""), the error will gone. If we
replace the content of snippet with "a = 1", the program will work well.
H
New submission from Xinmeng Xia :
"pprint" can transform unicode like "print". However, pprint fails to transform
non-breaking space('\240') . See the following example:
Python 3.10.0a2 (default, Nov 24 2020, 14:18:46)
[GCC 7.5.0] on linux
Type "help",
New submission from Xinmeng Xia :
The attached file "test_zipfile.py" is from test directory in cPython. We
delete irrelevant code. Running this code on Python 3.10 will lead to the
following erro
New submission from Xinmeng Xia :
Running attached "test_zipfile.py" on Python 3.10 will lead to the following
error messages:
Exception ignored in:
Traceback (most recent call las
Change by Xinmeng Xia :
--
type: -> compile error
___
Python tracker
<https://bugs.python.org/issue42858>
___
___
Python-bugs-list mailing list
Unsubscrib
Xinmeng Xia added the comment:
I get a little confused. So is it a bug in Python 3.5 and 3.6?
--
___
Python tracker
<https://bugs.python.org/issue42762>
___
___
New submission from Xinmeng Xia :
In the following program 1， method "__sizeof__()" is called and assigned
multiple times. The program can work well on Python 3.10. However if I change
"__sizeof__()" to "__sizeof__". Then a segmentation fault is reported. I
New submission from Xinmeng Xia :
The following thread program will cause Python3.10 parser "core dump" due to
missing “libgcc_s.so.1”. "pthread_cancel" cannot work correctly. I am wondering
is there any possible to install or link to libgcc_s.so.1 during
New submission from Xinmeng Xia :
The following program will lead to a incorrect behavior of Python parser. We
change all variable to integer( forcely transformed to string) via
ast.NodeTransformer. Then we compile the new code and execute it. It's
surprising that code like "1=
Xinmeng Xia added the comment:
>>python310 -V
Python 3.10.0a2
>>uname -v
#73~16.04.1-Ubuntu SMP Fri Sep 13 09:56:18 UTC 2019
Thank you!
--
___
Python tracker
<https://bugs.python
Xinmeng Xia added the comment:
>>uname -a
Linux xxm-System-Product-Name 4.15.0-64-generic #73~16.04.1-Ubuntu SMP Fri Sep
13 09:56:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>>uname -r
4.15.0-64-generic
>>lsb_release -a
No LSB modules are available.
Distributor ID:
Xinmeng Xia added the comment:
Sorry, my description is a little confusing. My points lie on function
'compile' and 'exec'. Yes, I agree. AST can be modified and don't correspond to
valid programs. But I don't think this invaild program can be compiled and
Xinmeng Xia added the comment:
Nice suggestion! I change the argument and I can' find segfault program in
transforming ast.Name. But I do find a segfault program in transforming
ast.BinOp!
Seeing the following example, this program will cause a segmentation fault on
Python 3.10. No
New submission from Xinmeng Xia :
For build-in function compile() in mode 'single', only single statement can be
well compiled. If we compile multiple statements, the parser will raise a
syntaxError. Seeing the following two programs, In program 1, 2 statement are
compiled. So
New submission from Xinmeng Xia :
In build-in function compile() of mode 'single', single statement can be well
compiled. (see program 1 and program 2). However, if we leave 4 blank spaces
before the end of triple-quotation mark of "if expression",(see program 3), Th
Change by Xinmeng Xia :
--
components: +Interpreter Core
___
Python tracker
<https://bugs.python.org/issue42918>
___
___
Python-bugs-list mailing list
Unsub
Xinmeng Xia added the comment:
The bytecode of c is as following:
0 LOAD_CONST 0 (1)
2 STORE_NAME 0 (d)
4 LOAD_CONST 1 (None)
6 RETURN_VALUE
===
Yes
Xinmeng Xia added the comment:
For sure! As soon as we validate this technique, we will open source it on
GitHub.
--
___
Python tracker
<https://bugs.python.org/issue42
Xinmeng Xia added the comment:
I see,Thank you!
--
___
Python tracker
<https://bugs.python.org/issue42762>
___
___
Python-bugs-list mailing list
Unsubscribe:
Xinmeng Xia added the comment:
Thank you. But I am not sure this is a recursion problem. Please see the
following example, I replace "__sizeof__" with "__class__". No segmentation
fault. Everything goes well.
mystr = "hello123"
pr
Xinmeng Xia added the comment:
Thank you for your kindly explanations! The output of the first program in
msg384799 behaves as expected from the view of AST compiling. Yes,I see now.
But for the second example in msg384879, the behaviors are inconsistent between
old Python version
New submission from Xinmeng Xia :
Seeing the following programs, we try to catch a recursive call error in
exception handling. The behaviors between Python 3.10.0a4 and older version
are inconsistent. The outputs are attached in the end. The output on Python
3.10.0a4 is very weird. Two
New submission from Xinmeng Xia :
In issue 42500, recursive calls in "Try-except" are resolved. This PR has fixed
the crashes of some programs, such as program 1. And the core dump error is
replaced with RecursiveError.
However, program 2 will not report a RecursiveError. The pr
Xinmeng Xia added the comment:
It seems that this bug won't be fixed. Should this issue be closed now?
--
___
Python tracker
<https://bugs.python.org/is
Xinmeng Xia added the comment:
No crash is reported anymore. The result is like following:
-
...
OSError: [Errno 24] Too many open files
OSError: [Errno 24] Too many open files
OSError: [Errno 24] Too many open files
OSError: [Errno 24] Too many
Xinmeng Xia added the comment:
I think the crash is fixed by this PR. I try other arguments. No crash is
reported. Thank you!
--
___
Python tracker
<https://bugs.python.org/issue42
Xinmeng Xia added the comment:
oh,I see. By the way, I set the argument of sys.setrecursionlimit to 10 in
this program and a segmentation fault is reported. Is that normal?
--
___
Python tracker
<https://bugs.python.org/issue42
New submission from Xinmeng Xia :
The following code recursively calls function test_forkserver(). However, the
output is not expected RecursionError(recursively calling) or OSError(too many
open files). An unexpected EOFError ( inside module multiprocessing, not this
code itself) is
New submission from Xinmeng Xia :
Python 3.6 can work well on old version of MacOS. When I upgrade MacOS to the
latest version Big Sur 11.2.3. Python 3.6 fails to start and crashes. Python
3.7, 3.8, 3.9 can perform well on the new version MacOS Big Sur 11.2.3. The
crash information attached
New submission from Xinmeng Xia :
Installation of latest Python 3.6.13 fails on MacOS Big Sur 11.2.3. The source
code is downloaded from python.org. Then we try to install it by commands
"./configure;sudo make;sudo make install". However the installation crashes.
The installatio
New submission from Xinmeng Xia :
Module bz2 fails to be imported on Ubuntu due to lack of '_bz2'. We try
"import bz2" on Mac, it can work well.
Errors on Ubuntu
==
>>import bz2
Traceback (most recent call last):
File
New submission from Xinmeng Xia :
In full grammar specification of Python 3.6 official documentation (Python 3.6
official documentation: https://docs.python.org/3.6/reference/grammar.html ),
we can find a very clear definition on the grammar about the usage of 'break'.
Accord
New submission from Xinmeng Xia :
When printing an assignment expression with unicode ܯ ( \U+072F) on the
command line, we get an unexpected result.
Example A:
>>> print(chr(1839)+" = 1")
ܯ = 1
Similar problems exist in plenty of characters of unicode.
--
component
New submission from Xinmeng Xia :
The snake game will report a crash in Python3:
Traceback (most recent call last):
File "/home/xxm/Desktop/instrument/datasetpy3/Snake_game/runGame.py",line 20,
in
w.addch(food[0], food[1], curses.ACS_PI)
TypeError: integer argument expected,
New submission from Xinmeng Xia :
Traceback (most recent call last):
File "/home/xxm/Desktop/instrument/datasetpy3/FrisPy/example.py", line 4, in
import FrisPy
File "/home/xxm/Desktop/instrument/datasetpy3/FrisPy/FrisPy/__init__.py",
line 5, in
from .disc im
New submission from Xinmeng Xia :
There is a bug in lib2to3. When dealing with this project "struts-scan" by
2to3,the following bug will show up.
Traceback (most recent call last):
File "/home/xxm/Desktop/instrument/datasetpy3/struts-scan/struts-scan.py
New submission from Xinmeng Xia :
In Python 2,the output is 1366. After converting by 2to3, the output is
1197.1463275484991
There exists bug in the conversion of 2to3. The output should be consistent for
original Python2 code and converted Python3 code.
At line 10 of this python file. The
New submission from Xinmeng Xia :
we run the converted Python3 code, the following error will happen:
Traceback (most recent call last):
File "/home/xxm/Desktop/instrument/datasetpy3/Labeled-LDA-Python/example.py",
line 50, in
llda_model.save_model_to_dir(save_model_dir)
Fi
1 - 100 of 101 matches
Mail list logo
