* David Malcolm: > The most recent one, and thus the first one I looked at (CID=1412982) > was a supposed "Resource Leak" in the get_cast_suggestion function I > introduced in r249461, where the local variable "trial" is supposedly > leaked (leading to 3 issues within Coverity overall, if I'm reading > things right, for the 3 ways in which a non-NULL value can be generated > and then fall out of scope).
Please keep in mind that the Coverity Scan terms of use specifically disallow such public discussion: “You will not publish any findings regarding or resulting from use of the Service or the Software”. I don't know if this also means that you cannot fix bugs identified by the service.
