Bug 10137 - Memory Leak's PATCH included
Summary: Memory Leak's PATCH included
Status: RESOLVED OBSOLETE
Alias: None
Product: gdb
Classification: Unclassified
Component: cli (show other bugs)
Version: 6.8
: P2 normal
Target Milestone: 6.8
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-09 20:05 UTC by Darryl L. Miles
Modified: 2022-03-01 23:45 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Patch for the memory leaks and a overlapping memcpy() (1.82 KB, patch)
2009-05-09 20:07 UTC, Darryl L. Miles 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darryl L. Miles 2009-05-09 20:05:59 UTC 
Originally I was investigating a specific reproducible memory leak so I stuck
valgrind on GDB and fixed 3 or 4 leaks which show up clearly once you iterate
1000s of command via the MI protocol interface.

Version: 6.8.50.20090509-cvs
Comment 1 Darryl L. Miles 2009-05-09 20:07:46 UTC 
Created attachment 3928 [details]
Patch for the memory leaks and a overlapping memcpy()

Patch for the memory leaks and a overlapping memcpy() case valgrind found.
Comment 2 Tom Tromey 2009-08-07 19:12:35 UTC 
Thanks for the patch.

The thing to do is send the patch plus a ChangeLog entry to the
gdb-patches list.
Also, if you do not have copyright assignment paperwork in place,
we will need that.  You can contact me off-list and I will get you
started, if you are willing.
Comment 3 Tom Tromey 2022-03-01 23:45:27 UTC 
We've fixed a ton of leaks and I think this patch must
also be long since obsolete.