Issue 60 in iperf: Memory leak

[ip...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 60 by devzone...@gmail.com: Memory leak
http://code.google.com/p/iperf/issues/detail?id=60

[src/iperf_api.c:1179]: (error) Memory leak: tcp
[src/locale.c:104]: (error) syntax error
[src/locale.c:334]: (error) Invalid number of character ({) when these
macros are defined: '__cplusplus'.


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[ip...@googlecode.com]

Comment #1 on issue 60 by jef.posk...@gmail.com: Memory leak
http://code.google.com/p/iperf/issues/detail?id=60

The two errors in locale.c were easily fixed, but I'm surprised that your
compiler noted them. It does syntax checking inside #ifdefs that are not
currently defined? That seems unusually persnickety. I like persnickety.

The supposed memory leak remains a mystery.

[ip...@googlecode.com]

Comment #2 on issue 60 by devzone...@gmail.com: Memory leak
http://code.google.com/p/iperf/issues/detail?id=60

[src/units.c:90]: (portability) scanf without field width limits can crash
with huge input data on libc versions older than 2.13-25. Add a field width
specifier to fix this problem:
%i => %3i

Sample program that can crash:

#include <stdio.h>
int main()
{
int a;
scanf("%i", &a);
return 0;
}

To make it crash:
perl -e 'print "5"x2100000' | ./a.out

[ip...@googlecode.com]

Comment #3 on issue 60 by jdu...@lbl.gov: Memory leak
http://code.google.com/p/iperf/issues/detail?id=60

Is this analysis coming from valgrind or something?

[ip...@googlecode.com]

Comment #4 on issue 60 by devzone...@gmail.com: Memory leak
http://code.google.com/p/iperf/issues/detail?id=60

@jdu,

Yes cppcheck, http://sourceforge.net/apps/trac/cppcheck/

[ip...@googlecode.com]

Comment #5 on issue 60 by devzone...@gmail.com: Memory leak
http://code.google.com/p/iperf/issues/detail?id=60

[src/iperf_api.c:1179]: (error) Memory leak: tcp

[src/iperf_api.c:1680]: (debug) inconclusive leak of sp: ; alloc ; use ; if
return ; return use ; }
[src/iperf_api.c:769]: (debug) uninitialized variables: bailout. can't
determine if this condition can be false when previous condition is false:
(Nwrite(test.ctrl_sck,&test.state,1,SOCK_STREAM)<0)
[src/iperf_api.c:1232]: (debug) uninitialized variables: bailout. can't
determine if this condition can be false when previous condition is false:
(test.stats_timer)

[ip...@googlecode.com]

Updates:
Owner: japos...@lbl.gov
Labels: Milestone-3.0-Release

Comment #6 on issue 60 by bltier...@lbl.gov: Memory leak
http://code.google.com/p/iperf/issues/detail?id=60

(No comment was entered for this change.)

[ip...@googlecode.com]

Updates:
Status: WontFix

Comment #7 on issue 60 by bltier...@lbl.gov: Memory leak
http://code.google.com/p/iperf/issues/detail?id=60

was not able to replicate
problem may be fixed.