From Fedora Project Wiki
Line 32: Line 32:
== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
[https://bugzilla.redhat.com/attachment.cgi?id=369008 example of complex backtrace] (relating to [https://bugzilla.redhat.com/show_bug.cgi?id=536786 bug 536786])
* Highest value: automatically display python frame information in PyEval_EvalFrameEx in gdb backtraces, including in ABRT:
* Highest value: automatically display python frame information in PyEval_EvalFrameEx in gdb backtraces, including in ABRT:
** python source file, line number, and function names
** python source file, line number, and function names
** values of locals, if available
** values of locals, if available
* name of function for wrapped C functions
* name of function for wrapped C functions


== Benefit to Fedora ==
== Benefit to Fedora ==

Revision as of 01:03, 22 December 2009

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Important.png
Set a watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
Note.png
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed



Easier Python Debugging

Summary

Owner

  • Email: <dmalcolm@redhat.com>

Current status

  • Targeted release: Fedora 41
  • Last updated: (DATE)
  • Percentage of completion: XX%


Detailed Description

example of complex backtrace (relating to bug 536786)

  • Highest value: automatically display python frame information in PyEval_EvalFrameEx in gdb backtraces, including in ABRT:
    • python source file, line number, and function names
    • values of locals, if available
  • name of function for wrapped C functions

Benefit to Fedora

Scope

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion