Re: [Live-devel] Unitialized memory in RTPReceptionStats

2013-04-06 Thread Ross Finlayson
> I have noticed that many items are not initialized on construction. > Mostly this shows up during incomplete usage by the programmer, me, but it is > important to note that the checks for null that are in the code fail when in > DEBUG on Windows. Have you found any examples of this in our

Re: [Live-devel] Unitialized memory in RTPReceptionStats

2013-04-06 Thread Jeff Shanab
or phone. From: live-devel-boun...@ns.live555.com [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson Sent: Friday, April 05, 2013 12:13 PM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Unitialized memory in RTPReceptionStats I know you don&#x

Re: [Live-devel] Unitialized memory in RTPReceptionStats

2013-04-05 Thread Ross Finlayson
> I know you don’t like valgrind tool I *do* like "valgrind". The problem with it, however, is that it frequently reports 'errors' that aren't really errors. Therefore, I generally don't pay attention when people send me "valgrind" reports, unless they can also note a specific problem in the c

[Live-devel] Unitialized memory in RTPReceptionStats

2013-04-05 Thread PROMONET Michel
Hi Ross, I know you don't like valgrind tool, but it reports use of uninitialized memory : Conditional jump or move depends on uninitialised value(s) (see: http://valgrind.org/docs/manual/mc-manual.html#mc-manual.uninitvals) at 0x1036E23: RTCPInstance::enqueueReportBlock(