Re: [Rd] Ctrl-C of functions that allocated mem

From: oliver <>
Date: Thu, 09 Jun 2011 13:32:52 +0200

On Wed, Jun 08, 2011 at 08:40:21PM -0400, Simon Urbanek wrote:
> On Jun 8, 2011, at 8:06 PM, oliver wrote:
> >
> > Hello,
> >
> >
> > what happens, when a function (R-extension in C), that allocated memory
> > (strdup(), malloc()/calloc() and so on), and is used in interactive mode, then
> > will be stopped via Ctrl-C?
> >
> > I would assume that there remains allocated memory,
> > which is not usable and also not accessable (hence no
> > way to free it).
> >
> > Are there any mechanisms in R that could help in rolling
> > back the allocation?
> >
> Yes, if you read R-exts:
> you would know that you're not supposed to use malloc/calloc at all and if you allow interruption ("regular" C code does not) R_alloc does what you asked about.


There are some pages I didn't read so far.

I'm just too unpatient....
...maybe should go on reading ;)

Thanks for the hint to the R-exts.html.

.... I hope there I also will find a solution for my filename-problem: want a char* on a filename, must use const char* (strdup() would match that issue), and I should not use my own allocation mechanisms. Then there must be something to address this.


   Oliver mailing list Received on Thu 09 Jun 2011 - 11:35:03 GMT

This quarter's messages: by month, or sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

All messages

Archive maintained by Robert King, hosted by the discipline of statistics at the University of Newcastle, Australia.
Archive generated by hypermail 2.2.0, at Thu 09 Jun 2011 - 13:20:17 GMT.

Mailing list information is available at Please read the posting guide before posting to the list.

list of date sections of archive