Re:A bug in GCC that may cause memory leaks in valid C++ pro...
by nuntius on Friday April 28, 2017 @12:01AM
(#14216788)
Instantly, as in next line of code? Yeah, probable human error (or auto-generated code).
Without being used? Not surprising. It is surprisingly common to allocate a variable, pass it to a function, and have the call never actually use the variable. Unwind, and the variable is destructed without use.
I've seen other nasty framework errors exposed by such (non-)usage patterns.
Without being used? Not surprising. It is surprisingly common to allocate a variable, pass it to a function, and have the call never actually use the variable. Unwind, and the variable is destructed without use.
I've seen other nasty framework errors exposed by such (non-)usage patterns.