swig/Examples/test-suite/r_memory_leak.i
Arnaud Barré 3fa5c8c652 Fix R memory leak on exception
There is a possible memory leak in case the SWIG_exception_fail macro
is called. The problem is related to its definition that call the
function Rf_warning. This function (as well as Rf_error) involves
a longjmp over C++ destructors on the stack. Thus, all the objects
allocated on the heap are not freed.

Closes #914
2020-01-30 20:43:39 +00:00

40 lines
832 B
OpenEdge ABL

%module r_memory_leak
%include <std_string.i>
%typemap(in) Foo* foo
{
$1 = new Foo;
}
%typemap(freearg) Foo* foo
{
printf(" \" Object deleted\"\n");
delete $1;
}
%typemap(out) Foo* verify_no_memory_leak
{
if ($1 == NULL)
SWIG_exception_fail(SWIG_RuntimeError, "Let's see how the bindings manage this exception!");
}
%typemap(scoerceout) Foo*
%{ if (!is.null($result) && !is.logical($result)) {$result <- new("$R_class", ref=$result) ;} %}
%inline %{
#include <string>
class Foo {
static unsigned count;
public:
Foo() { ++count; }
~Foo() { --count; }
static unsigned get_count() { return count; }
};
unsigned Foo::count = 0;
static Foo* trigger_internal_swig_exception(const std::string& message, Foo* foo)
{
return (message == "null") ? NULL : foo;
};
%}