[Bug binutils/6743] PATCH COMMITTED: new variable for malloc
H.J. Lu
hjl.tools@gmail.com
Mon Jul 14 01:25:00 GMT 2008
More information about the Binutils mailing list
Mon Jul 14 01:25:00 GMT 2008
- Previous message (by thread): [Bug binutils/6743] PATCH COMMITTED: new variable for malloc
- Next message (by thread): [Bug binutils/6743] PATCH COMMITTED: new variable for malloc
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Jul 13, 2008 at 05:12:20PM -0700, Craig Silverstein wrote: > It turns out a variable I thought would always point to the beginning > of the malloc-block, can actually change value. This was causing > crashes in some cases. I've fixed this by adding a new pointer, that > always points to the malloc-location, so we can always free it safely. > > I'm comitting this under the "obvious fix" principle. This is > probably the least obvious of the obvious fixes I've done so far, but > I hope it still safely falls into that category. > > craig > > --cut here-- > > 2008-07-13 Craig Silverstein <csilvers@google.com> > > * dwarf2.c (struct dwarf2_debug): New variable info_ptr_memory. > (find_line): Use info_ptr_memory instead of sec_info_ptr. > (_bfd_dwarf2_cleanup_debug_info): Likewise. > > Hi Craig, Thanks for fixing both PR ld/6741 and PR binutils/6743. I added those PRs in your ChangeLog entries. H.J.
- Previous message (by thread): [Bug binutils/6743] PATCH COMMITTED: new variable for malloc
- Next message (by thread): [Bug binutils/6743] PATCH COMMITTED: new variable for malloc
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list