summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_gdb.py
Commit message (Collapse)AuthorAgeFilesLines
* [3.11] gh-109972: Split test_gdb.py into test_gdb package (#109977) (… ↵Victor Stinner2023-10-041-1066/+0
| | | | | | | | | | | | | | | | | | | | | | | (#110343) [3.12] gh-109972: Split test_gdb.py into test_gdb package (#109977) (#110339) gh-109972: Split test_gdb.py into test_gdb package (#109977) Split test_gdb.py file into a test_gdb package made of multiple tests, so tests can now be run in parallel. * Create Lib/test/test_gdb/ directory. * Split test_gdb.py into multiple files in Lib/test/test_gdb/ directory. * Move Lib/test/gdb_sample.py to Lib/test/test_gdb/ directory. Update get_sample_script(): use __file__ to locate gdb_sample.py. * Move gdb_has_frame_select() and HAS_PYUP_PYDOWN to test_misc.py. * Explicitly skip test_gdb on Windows. Previously, test_gdb was skipped even if gdb was available because of gdb_has_frame_select(). (cherry picked from commit 8f324b7ecd2df3036fab098c4c8ac185ac07b277) (cherry picked from commit e7a61d34b7897ac6cff53add2ec03309a5ff8350)
* [3.11] gh-104736: Fix test_gdb tests on ppc64le with clang (GH-109360) (#109362)Miss Islington (bot)2023-09-131-0/+8
| | | | | | | | | | | gh-104736: Fix test_gdb tests on ppc64le with clang (GH-109360) Fix test_gdb on Python built with LLVM clang 16 on Linux ppc64le (ex: Fedora 38). Search patterns in gdb "bt" command output to detect when gdb fails to retrieve the traceback. For example, skip a test if "Backtrace stopped: frame did not save the PC" is found. (cherry picked from commit 44d9a71ea246e7c3fb478d9be62c16914be6c545) Co-authored-by: Victor Stinner <vstinner@python.org>
* [3.11] gh-91960: Skip test_gdb if gdb cannot retrive Python frames ↵Miss Islington (bot)2023-09-061-4/+3
| | | | | | | | | | | | | | | | | (GH-108999) (#109011) gh-91960: Skip test_gdb if gdb cannot retrive Python frames (GH-108999) Skip test_gdb if gdb is unable to retrieve Python frame objects: if a frame is "<optimized out>". When Python is built with "clang -Og", gdb can fail to retrive the 'frame' parameter of _PyEval_EvalFrameDefault(). In this case, tests like py_bt() are likely to fail. Without getting access to Python frames, python-gdb.py is mostly clueless on retrieving the Python traceback. Moreover, test_gdb is no longer skipped on macOS if Python is built with Clang. (cherry picked from commit fbce43a251488f666be9794c908a6613bf8ae260) Co-authored-by: Victor Stinner <vstinner@python.org>
* [3.11] gh-108416: Mark slow test methods with @requires_resource('cpu') ↵Serhiy Storchaka2023-09-031-0/+7
| | | | | | | (GH-108421) (GH-108799) Only mark tests which spend significant system or user time, by itself or in subprocesses. (cherry picked from commit f3ba0a74cd50274acdcd592d4ce8395b92492b7c)
* Do not run test_gdb when gdb embeds Python 2. (GH-31956)Inada Naoki2022-03-171-0/+3
|
* bpo-46600: Fix test_gdb.test_pycfunction() for clang -Og (GH-31058)Victor Stinner2022-02-011-11/+14
| | | | | | | | Fix test_gdb.test_pycfunction() for Python built with clang -Og. Tolerate inlined functions in the gdb traceback. When _testcapimodule.c is built by clang -Og, _null_to_none() is inlined in meth_varargs() and so gdb returns _null_to_none() as the frame #1. If it's not inlined, meth_varargs() is the frame #1.
* bpo-45637: Remove broken fallback in gdb helpers to obtain frame variable ↵Pablo Galindo Salgado2021-11-091-0/+2
| | | | (GH-29257)
* bpo-45256: Avoid C calls for most Python to Python calls. (GH-28937)Mark Shannon2021-10-181-25/+27
| | | | | | * Avoid making C calls for most calls to Python functions. * Change initialize_locals(steal=true) and _PyTuple_FromArraySteal to consume the argument references regardless of whether they succeed or fail.
* bpo-45256: Remove the usage of the C stack in Python to Python calls (GH-28488)Pablo Galindo Salgado2021-10-091-3/+23
| | | | Ths commit inlines calls to Python functions in the eval loop and steals all the arguments in the call from the caller for performance.
* bpo-45207: Make test_gdb.test_pycfunction() quiet (GH-28355)Victor Stinner2021-09-151-3/+11
| | | | | | test_gdb.test_pycfunction() now ignores gdb stderr, it no longer logs messages like: Function "meth_varargs" not defined.
* bpo-44821: Eagerly assign __dict__ for new objects. (GH-27589)Mark Shannon2021-08-041-1/+1
|
* bpo-44032: Move data stack to thread from FrameObject. (GH-26076)Mark Shannon2021-05-211-5/+6
| | | | | | | | | | | | | | | | * Remove 'zombie' frames. We won't need them once we are allocating fixed-size frames. * Add co_nlocalplus field to code object to avoid recomputing size of locals + frees + cells. * Move locals, cells and freevars out of frame object into separate memory buffer. * Use per-threadstate allocated memory chunks for local variables. * Move globals and builtins from frame object to per-thread stack. * Move (slow) locals frame object to per-thread stack. * Move internal frame functions to internal header.
* bpo-41473: Reenable test_gdb on gdb 9.2 and newer (GH-23637)Victor Stinner2020-12-041-5/+0
| | | | https://bugzilla.redhat.com/show_bug.cgi?id=1866884 is fixed in gdb 10.1 (failed to reproduce on gdb-10.1-1.fc34.aarch64).
* bpo-41473: Skip test_gdb with gdb 9.2 to work around gdb bug (GH-21768)Victor Stinner2020-08-071-0/+5
| | | | | | gdb 9.2 on Fedora Rawhide is not reliable, see: * https://bugs.python.org/issue41473 * https://bugzilla.redhat.com/show_bug.cgi?id=1866884
* bpo-34401: Fix test_gdb for HP GDB version string (GH-20804)Victor Stinner2020-06-111-1/+2
| | | | | | | | The GDB provided by HPE on HP-UX contains a modified version string. Therefore the tests fail. Adapt the regex to match that string. Patch by Michael Osipov. Co-Authored-by: Michael Osipov <michael.osipov@siemens.com>
* bpo-40436: Fix code parsing gdb version (GH-19792)Victor Stinner2020-04-291-2/+8
| | | test_gdb and test.pythoninfo now check gdb command exit code.
* bpo-40019: Skip test_gdb if Python was optimized (GH-19081)Victor Stinner2020-03-201-0/+9
| | | | test_gdb now skips tests if it detects that gdb failed to read debug information because the Python binary is optimized.
* bpo-38239: Fix test_gdb for Link Time Optimization (LTO) (GH-16422)Victor Stinner2019-09-261-2/+9
|
* bpo-37499: Test various C calling conventions (GH-15776)Petr Viktorin2019-09-101-31/+50
| | | | | | | | | | Add functions with various calling conventions to `_testcapi`, expose them as module-level functions, bound methods, class methods, and static methods, and test calling them and introspecting them through GDB. https://bugs.python.org/issue37499 Co-authored-by: Jeroen Demeyer <J.Demeyer@UGent.be> Automerge-Triggered-By: @pganssle
* test_gdb: use unittest test discovery (GH-15405)Victor Stinner2019-08-231-11/+5
| | | | | | | Replace test.support.run_unittest() with unittest.main() to automatically discover test cases, instead of having an maintaing manually a list which may be incomplete. Remove also an unused variable.
* bpo-36974: separate vectorcall functions for each calling convention (GH-13781)Jeroen Demeyer2019-07-051-4/+4
|
* bpo-37362: test_gdb now ignores stderr (GH-14287)Victor Stinner2019-06-211-34/+13
| | | | | test_gdb no longer fails if it gets an "unexpected" message on stderr: it now ignores stderr. The purpose of test_gdb is to test that python-gdb.py commands work as expected, not to test gdb.
* test_gdb.test_pycfunction: test more calling conventions (GH-13668)Petr Viktorin2019-06-021-21/+34
| | | | | As the code paths for various METH_* conventions are diverging due to optimizations, we should check they continue to be covered by GDB integration.
* bpo-36974: Fix GDB integration (GH-13665)Petr Viktorin2019-05-291-1/+1
| | | | | | | | | | | As it changes the way functions are called, the PEP 590 implementation skipped the functions that the GDB integration is looking for (by name) to find function calls. Looking for the new helper `cfunction_call_varargs` hopefully fixes the tests, and thus buildbots. The changed frame nuber in test_gdb is due to there being fewer C calls when calling a built-in method.
* bpo-37023: Skip test_gdb under PGO (GH-13555)Steve Dower2019-05-241-1/+5
|
* bpo-35202: Remove unused imports in tests. (GH-10561)Srinivas Thatiparthy (శ్రీనివాస్ తాటిపర్తి)2018-11-161-1/+0
|
* bpo-21263: Skip test_gdb when python has been compiled with LLVM clang ↵Lysandros Nikolaou2018-11-041-0/+5
| | | | (GH-10318)
* bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection ↵Victor Stinner2018-10-091-1/+32
| | | | | | | | | | | | | -O0 (GH-9656) When Python is built with the intel control-flow protection flags, -mcet -fcf-protection, gdb is not able to read the stack without actually jumping inside the function. This means an extra 'next' command is required to make the $pc (program counter) enter the function and make the stack of the function exposed to gdb. Co-Authored-By: Marcel Plch <gmarcel.plch@gmail.com> (cherry picked from commit 9b7c74ca32d1bec7128d550a9ab1b2ddc7046287)
* bpo-34537: Fix test_gdb:test_strings with LC_ALL=C (GH-9483)Elvis Pranskevichus2018-09-221-1/+14
| | | | | | | | We cannot simply call locale.getpreferredencoding() here, as GDB might have been linked against a different version of Python with a different encoding and coercion policy with respect to PEP 538 and PEP 540. Thanks to Victor Stinner for a hint on how to fix this.
* bpo-34007: Skip traceback tests if the Program Counter is not available. ↵Pablo Galindo2018-08-311-0/+9
| | | | | | | | | (GH-9018) Sometimes some versions of the shared libraries that are part of the traceback are compiled in optimised mode and the Program Counter (PC) is not present, not allowing gdb to walk the frames back. When this happens, the Python bindings of gdb raise an exception, making the test impossible to succeed.
* Revert "bpo-32962: Fix test_gdb failure in debug build with -mcet ↵Victor Stinner2018-06-151-9/+2
| | | | | -fcf-protection -O0 (GH-6754)" (#7723) This reverts commit 9b7c74ca32d1bec7128d550a9ab1b2ddc7046287.
* bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection ↵Marcel Plch2018-06-151-2/+9
| | | | | | | | | -O0 (#6754) When Python is built with the intel control-flow protection flags, -mcet -fcf-protection, gdb is not able to read the stack without actually jumping inside the function. This means an extra 'next' command is required to make the $pc (program counter) enter the function and make the stack of the function exposed to gdb.
* bpo-31370: Remove support for threads-less builds (#3385)Antoine Pitrou2017-09-071-12/+0
| | | | | | * Remove Setup.config * Always define WITH_THREAD for compatibility.
* Issue #29263: LOAD_METHOD support for C methodsINADA Naoki2017-02-021-1/+1
| | | | Calling builtin method is at most 10% faster.
* Fix test_gdb.test_wrapper_call() on Python 2Victor Stinner2017-02-011-2/+2
| | | | Issue #29367. On Python 2, __init__ name is render as u'__init__'.
* Make test_gdb.test_wrapper_call() make reliableVictor Stinner2017-02-011-3/+2
| | | | | Issue #29367. Use two break points to prevent breakpoint during Python initialization.
* python-gdb.py supports method-wrapperVictor Stinner2017-02-011-1/+20
| | | | | Issue #29367: python-gdb.py now supports also method-wrapper (wrapperobject) objects.
* Update and enhance python-gdb.pyVictor Stinner2017-01-181-1/+1
| | | | | | | | Issue #29259: * Detect PyCFunction is the current frame, not only in the older frame * Ignore PyCFunction_Call() since it now calls _PyCFunction_FastCallDict(), and _PyCFunction_FastCallDict() is already detected
* Issue #28770: Update python-gdb.py for fastcallsVictor Stinner2016-11-221-10/+10
| | | | | | | | Frame.is_other_python_frame() now also handles _PyCFunction_FastCallDict() frames. Thanks to the new code to handle fast calls, python-gdb.py is now also able to detect the <built-in id method of module ...> frame.
* Issue #28023: Fix python-gdb.py didn't support new dict implementationINADA Naoki2016-11-221-6/+3
|
* #27364: fix "incorrect" uses of escape character in the stdlib.R David Murray2016-09-081-6/+6
| | | | | | | And most of the tools. Patch by Emanual Barry, reviewed by me, Serhiy Storchaka, and Martin Panter.
* Implement compact dictVictor Stinner2016-09-081-0/+3
| | | | | | | | | | | | Issue #27350: `dict` implementation is changed like PyPy. It is more compact and preserves insertion order. _PyDict_Dummy() function has been removed. Disable test_gdb: python-gdb.py is not updated yet to the new structure of compact dictionaries (issue #28023). Patch written by INADA Naoki.
* get skipIf from the right placeBenjamin Peterson2016-09-071-1/+1
|
* Adds test.support.PGO and skips tests that are not useful for PGO.Steve Dower2016-09-071-0/+1
|
* merge 3.5 (#27969)Benjamin Peterson2016-09-061-0/+1
|\
| * suppress stderr output when checking gdb (closes #27969)Benjamin Peterson2016-09-061-0/+1
| |
* | MergeRaymond Hettinger2016-08-261-1/+1
|\ \ | |/
| * Issue 19504: Change "customise" to "customize" American spelling.Raymond Hettinger2016-08-261-1/+1
| |
| * Backport test_gdb fix for s390x buildbotsVictor Stinner2016-04-191-17/+7
| |
* | Issue #23277: Remove unused imports in tests.Serhiy Storchaka2016-04-241-1/+0
| |
generated by cgit v0.12 at 2025-09-13 23:53:43 (GMT)