From Fedora Project Wiki

(Indent <pre> tags. Still not sure what "meaningful information" means for debugging)
(convert to new category system)
Line 18: Line 18:
#* please see [[Features/EasierPythonDebugging#How_To_Test|EasierPythonDebuggingTests]] for more information.
#* please see [[Features/EasierPythonDebugging#How_To_Test|EasierPythonDebuggingTests]] for more information.
}}
}}
[[Category:ABRT_Test_Cases]]
[[Category:Package_abrt_test_cases]]

Revision as of 16:21, 13 January 2011

Description

This test case tests the functionality of the ABRT together with EasierPythonDebugging.


How to test

  1. Run the following python script that abuse the ctypes module in such a way as to cause /usr/bin/python to segfault/abort.
    1. First, cause a segfault 
      

      python -c "import ctypes; ctypes.string_at(0xffffffff)"
      

      Segmentation fault (core dumped)
      2. 

    2. Next, cause 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)
    2. 

  2. Next, repeat all of the above for python3
    3. 

  3. Finally, repeat the steps for python3-debuginfo


Expected Results


  1. In each case, there should be meaningful information at the Python level, as well as at the C level in the bactrace.

Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_python_better_debugging&oldid=215241"