Re: [Live-devel] Valgrind uninitialised values inside live555

2021-08-17 Thread Ba Jinsheng
Hi, I think a possible reason is the compilation optimization. Try to use "-O0" instead of "-O2" to compile the Live555. It may reduce the uninitialized errors. Best regards, Jinsheng Ba -Original Message- From: live-devel On Behalf Of Ross Finlayson Sent: Wednesday, August 18, 2021 2

Re: [Live-devel] Valgrind uninitialised values inside live555

2021-08-17 Thread Ross Finlayson
Not everything that ‘valgrind’ reports is actually an error. In each case, you need to look at the code to see if there’s really an error there. > For example I found this code inside GroupsockHelper.cpp: > > > static Boolean getSourcePort0(int socket, portNumBits& resultPortNum/*host > orde

[Live-devel] Valgrind uninitialised values inside live555

2021-08-17 Thread Костромин Дмитрий Андреевич
Hello, du debugging our project i detected some conditional jumps on uninitialised value. See Valgrind log below =79825== Thread 23: ==79825== Conditional jump or move depends on uninitialised value(s) ==79825==    at 0x650BEAB: setPortNum(sockaddr_storage&, unsigned short) (NetAddress.cpp:517)