From Fedora Project Wiki
Description
This test case tests the functionality of the ABRT together with EasierPythonDebugging.
How to test
- Run the following python script that abuse the
ctypes
module in such a way as to cause/usr/bin/python
to segfault/abort.- First, cause a segfault (triggering a core dump)
- python -c "import ctypes; ctypes.string_at(0xffffffff)"
- Segmentation fault (core dumped)
- Next, cause an assertion failure (triggering a core dump)
- python -c "import ctypes; ctypes.string_at(0x0)"
- python: Objects/stringobject.c:115: PyString_FromString: Assertion `str != ((void *)0)' failed.
- Aborted (core dumped)
- First, cause a segfault (triggering a core dump)
- Next, repeat all of the above for
python3
- Finally, repeat the steps for
python3-debuginfo
Expected Results
- In each case, the C-level backtrace in the ABRT report ought to contain details on the Python objects that were present in the C stack frames. For example, it ought to be possible to see repr()-style printings of the Python objects, rather than just hexadecimal addresses.
- please see EasierPythonDebuggingTests for more information.
- Note that this does not work well on x86_64