Bug 194 – TCP Socket valgrind error

Bug 194 - TCP Socket valgrind error


Summary:	TCP Socket valgrind error

Attachments
./waf --regression --regression-tests=test-tcp-large-transfer --valgrind 2>&1 \| tee /tmp/valgrind.log (3.12 KB, text/plain) 2008-05-29 07:20 UTC, Gustavo J. A. M. Carneiro	Details
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 Gustavo J. A. M. Carneiro 2008-05-29 07:15:18 UTC

"./waf --regression --valgrind" detects a valgrind error.  m_wouldBlock in TcpSocketImpl may be used uninitialized.

Comment 1 Gustavo J. A. M. Carneiro 2008-05-29 07:20:01 UTC

Created attachment 141 [details]
./waf --regression --regression-tests=test-tcp-large-transfer --valgrind 2>&1 | tee /tmp/valgrind.log

Comment 2 Gustavo J. A. M. Carneiro 2008-05-29 09:53:14 UTC

This valgrind error is strange; I see nothing wrong with the code, actually...

Comment 3 Gustavo J. A. M. Carneiro 2008-05-29 10:12:07 UTC

Found the problem.  There are two TcpSocketImpl constructors, and one of them was not initializing m_wouldBlock.

Comment 4 Mathieu Lacage 2008-05-29 12:21:55 UTC

*** Bug 193 has been marked as a duplicate of this bug. ***