Hi Ross,
Clearly you right, memory is surely allocated, and it will not end with a
segmentation violation.
I will put an exception in valgrind rules, but using unitilalized memory is
probably not a good practice.
In fact what's annoy me is to keep align a valgrind exception (or a patch) up
to date with a live555 release.
Best Regards,
Michel.
[@@THALES GROUP RESTRICTED@@]
De : live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] De la part de Ross Finlayson
Envoyé : mardi 24 janvier 2012 00:34
À : LIVE555 Streaming Media - development & use
Objet : Re: [Live-devel] use of unitialized memory in our_MD5End
In any case, this isn't a concern, because we're using MD5 here to generate a
'pseudo-random' value. It doesn't matter if some of the memory that MD5 reads
happens to be 'uninitialized'.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
