Re: [reSIProcate] [patch] possible memory corruption in SDP codec handling
Scott,
Did you ever look over this? Should I commit it?
Aron Rosenberg
Sr. Director, Engineering,
LifeSize, a division of Logitech
On Mon, Nov 7, 2011 at 6:12 AM, Robert Szokovacs
<robert.szokovacs@xxxxxxxxxxx> wrote:
Hi,
In a usual valgrind run, we noticed that is we call
SdpContents::Session::Medium::codecs() then copy the Medium object, we get
memory reads from places we should not access. The bug was tracked down to be
a misunderstaning between Codec::parse() and the Medium's AttributeHelper, the
AttributeHelper free's up the memory that was used by parse(). Patch and
testcase to reproduce attached.
br
Szo
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel