| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The faulthandler module now detects if a fatal error occurs during a
garbage collector collection (only if all_threads is true).
(cherry picked from commit d19163912bfc790283724f05328bd31e4e65003d)
|
|
|
|
|
|
|
|
|
| |
- Enum warning in test_faulthandler
- backslash warning in test_ipaddress
(cherry picked from commit 652bcd9f9cd2ed89b5fa958f8456556aa43b48cc)
Co-authored-by: Ethan Furman <ethan@stoneleaf.us>
Co-authored-by: Ethan Furman <ethan@stoneleaf.us>
|
|
|
|
| |
* Rename _Py_module_names to _Py_stdlib_module_names.
* Rename Python/module_names.h to Python/stdlib_module_names.h.
|
|
|
|
| |
Add sys.module_names, containing the list of the standard library
module names.
|
| |
|
|
|
|
|
|
|
| |
The Py_FatalError() function and the faulthandler module now dump the
list of extension modules on a fatal error.
Add _Py_DumpExtensionModules() and _PyModule_IsExtension() internal
functions.
|
|
|
| |
Move faulthandler._fatal_error() to _testcapi.fatal_error().
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Py_FatalError() function is replaced with a macro which logs
automatically the name of the current function, unless the
Py_LIMITED_API macro is defined.
Changes:
* Add _Py_FatalErrorFunc() function.
* Remove the function name from the message of Py_FatalError() calls
which included the function name.
* Update tests.
|
|
|
|
|
| |
test.support: run_python_until_end(), assert_python_ok() and
assert_python_failure() functions no longer strip whitespaces from
stderr.
|
|
|
|
| |
dump_traceback_later() and cancel_dump_traceback_later() functions of
the faulthandler module are always available since Python 3.7.
|
| |
|
|
|
|
| |
Fix faulthandler.cancel_dump_traceback_later() call
if cancel_dump_traceback_later() was not called previously.
|
| |
|
|
|
|
|
|
| |
As in title, expose C `raise` function as `raise_function` in `signal` module. Also drop existing `raise_signal` in `_testcapi` module and replace all usages with new function.
https://bugs.python.org/issue35568
|
| |
|
|
|
|
|
|
|
| |
Also skip the same tests when using the undefined behavior sanitizer
as they much with the output.
Updates a regex in another test to use multi-line mode so that the ubsan
buildbot should pass again rather than also adding a skip to that one.
|
|
|
|
|
| |
Add Clang Memory Sanitizer build instrumentation to work around
false positives from the socket and time modules as well as skipping
a couple test_faulthandler tests.
|
| |
|
|
|
| |
This reverts commit 8fbbdf0c3107c3052659e166f73990b466eacbb0.
|
|
|
|
|
|
|
|
| |
* Add support.MS_WINDOWS: True if Python is running on Microsoft Windows.
* Add support.MACOS: True if Python is running on Apple macOS.
* Replace support.is_android with support.ANDROID
* Replace support.is_jython with support.JYTHON
* Cleanup code to initialize unix_shell
|
|
|
|
| |
test_asycio: remove also aio_path which was used when asyncio was
developed outside the stdlib.
|
|
|
|
| |
Remove the test.support.requires_android_level decorator.
|
|
|
|
|
|
| |
bpo-31701: On Windows, faulthandler.enable() now ignores MSC and COM
exceptions.
|
|
|
|
|
|
| |
* Remove Setup.config
* Always define WITH_THREAD for compatibility.
|
|
|
|
| |
On Windows 8, 8.1 and 10 at least, the exit code is the exception
code (no bit is cleared).
|
|
|
|
|
|
|
|
|
|
| |
on Windows (#1924)
* bpo-30557: faulthandler now correctly filters and displays exception codes on Windows
* Adds test for non-fatal exceptions.
* Adds bpo number to comment.
|
|
|
|
|
|
|
|
|
|
|
|
| |
* bpo-30125: Cleanup faulthandler.c
* Use size_t type for iterators
* Add { ... }
* bpo-30125: Fix faulthandler.disable() on Windows
On Windows, faulthandler.disable() now removes the exception handler
installed by faulthandler.enable().
|
| |
|
|
|
|
|
| |
with a cosmetic change to add a commit message with the issue number,
missing from the previous two commits.
|
| |
|
|
|
|
| |
but not in the expressions. Also, require expressions to begin and end with literal curly braces.
|
|
|
|
|
|
|
| |
And most of the tools.
Patch by Emanual Barry, reviewed by me, Serhiy Storchaka, and
Martin Panter.
|
|
|
|
| |
before beta 2. I also need to look in to why test_tools/test_unparse fails with the files that are now being skipped.
|
|\
| |
| |
| | |
messages.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Issue #23848, #26622:
* faulthandler now only logs fatal Windows exceptions.
* write error code as decimal, not as hexadecimal
* replace "Windows exception" with "Windows fatal exception"
|
| |
| |
| |
| |
| |
| | |
Issue #23848: On Windows, faulthandler.enable() now also installs an exception
handler to dump the traceback of all Python threads on any Windows exception,
not only on UNIX signals (SIGSEGV, SIGFPE, SIGABRT).
|
|/
|
|
|
|
|
|
|
|
|
| |
Issue #26563:
* Add _PyGILState_GetInterpreterStateUnsafe() function: the single
PyInterpreterState used by this process' GILState implementation.
* Enhance _Py_DumpTracebackThreads() to retrieve the interpreter state from
autoInterpreterState in last resort. The function now accepts NULL for interp
and current_tstate parameters.
* test_faulthandler: fix a ResourceWarning when test is interrupted by CTRL+c
|
|
|
|
| |
Issue #26558.
|
|
|
|
| |
Patch by Christie Wilson.
|
|
|
|
| |
subprocess doesn't support pass_fds on Windows.
|
|
|
|
| |
functions of faulthandler now accept file descriptors. Patch by Wei Wu.
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
mode. Explicitly remove the PYTHONFAULTHANDLER environment variable before
launching a child interpreter when its presence would impact the test (the
reason -E was being used in the first place).
This enables running the test in an environment where other Python environment variables must be set in order for things to run (such as using PYTHONHOME to
tell an embedded interpreter where it should think it lives).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
mode. Explicitly remove the PYTHONFAULTHANDLER environment variable before
launching a child interpreter when its presence would impact the test (the
reason -E was being used in the first place).
This enables running the test in an environment where other Python environment
variables must be set in order for things to run (such as using PYTHONHOME to
tell an embedded interpreter where it should think it lives).
|
|\ \
| |/
| |
| |
| |
| |
| | |
_read_null(), because _read_null() cannot be used on AIX. On AIX, reading from
NULL is allowed: the first page of memory is a mapped read-only on AIX.
_read_null() and _sigabrt() don't accept parameters.
|
| |
| |
| |
| |
| | |
because _read_null() cannot be used on AIX. On AIX, reading from NULL is
allowed: the first page of memory is a mapped read-only on AIX.
|
|\ \
| |/ |
|
| | |
|
|\ \
| |/
| |
| | |
Patch written by Xavier de Gaye.
|