On Wed, 2016-02-03 at 10:42 +0000, Andrew Cooper wrote: > On 03/02/16 10:37, Ian Campbell wrote: > > George, > > > > Looks like xentrace is the only maintained component which uses this. > > so > > tag ;-) > > > > On Tue, 2016-02-02 at 20:23 -0800, scan-ad...@coverity.com wrote: > > > * CID 1351228: (RESOURCE_LEAK) > > > /tools/libxc/xc_tbuf.c: 73 in xc_tbuf_get_size() > > > /tools/libxc/xc_tbuf.c: 77 in xc_tbuf_get_size() > > Coverity is reporting these as new in 41b0aa569adb..9937763265d9 > > although > > the file hasn't changed. However it does look correct that t_info is > > being > > leaked by various paths in this function. > > It is "new"ly spotted because xc_map_foreign_range() is now a straight > function call rather than a function pointer pointing at functions with > different behaviours.
That makes sense, thanks. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
