[Valgrind-users] Syscall param socketcall.accept(addr) points to unaddressable byte(s)

Hi I have checked a TCP-server which i wrote with valgrind-3.4.0, and encountered these errors: ==15611== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 17 from 1) ==15611== ==15611== 1 errors in context 1 of 2: ==15611== Syscall param socketcall.accept(addr) points to unaddressable byte(s)

Re: [Valgrind-users] Syscall param socketcall.accept(addr) points to unaddressable byte(s)

On Wed, Jan 28, 2009 at 11:06 AM, jody jody@gmail.com wrote: Hi I have checked a TCP-server which i wrote with valgrind-3.4.0, and encountered these errors: ==15611== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 17 from 1) ==15611== ==15611== 1 errors in context 1 of 2:

Re: [Valgrind-users] Syscall param socketcall.accept(addr) points to unaddressable byte(s)

On Wed, 28 Jan 2009 11:06:37 +0100 jody jody@gmail.com wrote: Hi I have checked a TCP-server which i wrote with valgrind-3.4.0, and encountered these errors: ==15611== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 17 from 1) ==15611== ==15611== 1 errors in context 1 of 2:

Re: [Valgrind-users] Syscall param socketcall.accept(addr) points to unaddressable byte(s)

Thanks for the explanation - that fixed the issue! Jody On Wed, Jan 28, 2009 at 11:27 AM, Tom Hughes t...@compton.nu wrote: jody wrote: I simplified the server to the point where it only calls accept (see below), and the errors still prevail. I compile it with g++ -g -Wall dummysrv.cpp