Features/MemoryDebuggingTools

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
m (Comments and Discussion)
(Benefit to Fedora)
Line 38: Line 38:
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 +
This feature could be of great use to developers and system administrators: it provides a new way of analyzing how a process uses memory, without requiring advance planning.
 +
 +
It is unique to Fedora (it makes [https://fedorahosted.org/gdb-heap/wiki#Compatibilitywithgdbversions heavy use of the gdb/python integration we have in Fedora]), and was developed by a Fedora contributor (who is a Red Hat engineer).
  
 
== Scope ==
 
== Scope ==

Revision as of 22:31, 8 July 2010


Contents

Memory Debugging Tools

Summary

The gdb debugger has been extended with new commands that make it easier to track down and fix excessive memory usage within programs and libraries.

This functionality was created by Fedora contributor David Malcolm, and we believe it is unique to Fedora.

Owner

  • Email: <dmalcolm@redhat.com>

Current status

  • Targeted release: Fedora 22
  • Last updated: 2010-07-08
  • Percentage of completion: 20%

Preparing upstream project for initial launch: https://fedorahosted.org/gdb-heap/

Initial version of code uploaded

Upstream tickets:


Detailed Description

Benefit to Fedora

This feature could be of great use to developers and system administrators: it provides a new way of analyzing how a process uses memory, without requiring advance planning.

It is unique to Fedora (it makes heavy use of the gdb/python integration we have in Fedora), and was developed by a Fedora contributor (who is a Red Hat engineer).

Scope

How To Test

User Experience

Dependencies

There's a baseline of functionality that I'm developing on top of Fedora 13's gdb.

Some features require additional work in gdb, which I've filed RFE bugs for. Naturally this will require coordination with gdb to ensure that they land in Fedora 14:

  • RHBZ #610241: RFE: please expose "info symbol ADDRESS" in the python API
  • RHBZ #610249: RFE: notification about changes in the inferior process


Contingency Plan

None necessary, simply remove the package

Documentation

Release Notes

Comments and Discussion