From eb975ce88069fad7cad7657a846268b5305f239e Mon Sep 17 00:00:00 2001 From: Luis de Bethencourt Date: Fri, 6 Feb 2015 14:43:22 +0000 Subject: [PATCH] wavparse: fix which stop variable is used in assignment Assignment is done to variable segment.stop when the intention was to assign to local variable stop. Instead of overwriting it, the value is now clamped and segment.stop is set to it soon after. CID #1265773 --- gst/wavparse/gstwavparse.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gst/wavparse/gstwavparse.c b/gst/wavparse/gstwavparse.c index 2f5698b..41d5151 100644 --- a/gst/wavparse/gstwavparse.c +++ b/gst/wavparse/gstwavparse.c @@ -2348,8 +2348,8 @@ gst_wavparse_sink_event (GstPad * pad, GstObject * parent, GstEvent * event) } if (stop > 0) { end_offset = stop; - segment.stop -= wav->datastart; - segment.stop = MAX (stop, 0); + stop -= wav->datastart; + stop = MAX (stop, 0); } if (wav->segment.format == GST_FORMAT_TIME) { guint64 bps = wav->bps; -- 2.7.4