Incorrectly used free() in _psutil_osx.c

[giampaolo]

From alexey.p...@qik.com on December 23, 2011 16:18:40

free(fds_pointer);
...
fdp_pointer = &fds_pointer[i];

fds_pointer is freed, then accessed.

Original issue: http://code.google.com/p/psutil/issues/detail?id=240

[giampaolo]

From alexey.p...@qik.com on December 23, 2011 07:20:24

It's for 0.4.1. There is one more similar bug in trunk.

[giampaolo]

From g.rodola on December 23, 2011 11:25:53

Can you provide a patch?
@Jay: my virtualized OSX box is gone; can you look into this?

Labels: OpSys-OSX

[giampaolo]

From jlo...@gmail.com on December 23, 2011 11:54:59

Summary: Incorrectly used free() in _psutil_osx.c

[giampaolo]

From jlo...@gmail.com on December 23, 2011 11:55:51

Thanks for the report, there were two functions affected by this (incorrectly 
using free() on a pointer that was still in use later in the function. Fixed in r1244

Status: FixedInSVN

[giampaolo]

From g.rodola on January 30, 2012 04:19:51

Labels: Milestone-0.5.0

[giampaolo]

From g.rodola on April 16, 2012 08:30:51

After r1244 I see a lot of these errors:

    python(910) malloc: *** error for object 0xa9a6d0: Non-aligned pointer 
being freed (2)
*** set a breakpoint in malloc_error_break to debug

    python(910) malloc: *** error for object 0x1137800: double free
*** set a breakpoint in malloc_error_break to debug

They go away if I remove the "free(fds_pointer);" lines.

Status: ReOpened

[giampaolo]

From g.rodola on April 16, 2012 08:43:35

Fixed in r1285 .

Status: FixedInSVN

[giampaolo]

From g.rodola on June 27, 2012 11:54:03

0.5.0 is finally out. Closing out as fixed.

Status: Fixed

[giampaolo]

From g.rodola on March 02, 2013 04:06:19

Updated csets after the SVN -> Mercurial migration: r1244 == revision 
c624cdc5374b r1285 == revision 50786548c5c6