R devel - Jul 2013 - unmapped memory core dump with pure R program?

dear R developers---I am running a pure R program on the stock binary
debian (ubuntu) 64-bit linux distribution, 3.0.1.  for identification,

20abb3a1d917bce52a10dd40cb47b82b  /usr/lib/R/bin/exec/R
58ebc91f143f752610c8dbe22182f3f3  /usr/lib/libR.so


my R program loads 5 big matrices (about 1GB each)and rbind's them, all on
a 16GB machine.  alas, in one particular run, I am getting a mysterious

Error in rbind(deparse.level, ...) :
  'pairlist' object cannot be coerced to type 'double'

so I dropped into the R debugger (option(error=recover)) and tried to do
the rbind by hand again to figure out what this error message means in this
context.  (it works just fine with other combinations.)  when I thus am
trying to run it again, I am getting a

Browse[1]> head(rbind(dm,db))

 *** caught segfault ***
address 0x10, cause 'memory not mapped'

Traceback:
 1: rbind(deparse.level, ...)
 2: rbind(dm, db)
 3: head(rbind(dm, db))
 4: eval(expr, envir, enclos)
...

I then created a core dump (where R prompts me), which goes for 82 levels
(to _start), so its not an infinite recursion problem, but it does seem to
recurse some.  I don't have symbols in my R binary, so the location may not
be useful, but I thought I would let you guys know.  alas

(gdb) bt
#0  0x00007ff956be3857 in ?? () from /usr/lib/R/lib/libR.so
#1  0x00007ff956be67d3 in Rf_allocVector () from /usr/lib/R/lib/libR.so
#2  0x00007ff956b90338 in ?? () from /usr/lib/R/lib/libR.so
#3  0x00007ff956b8fcfa in ?? () from /usr/lib/R/lib/libR.so
#4  0x00007ff956b90875 in Rf_duplicate () from /usr/lib/R/lib/libR.so
#5  0x00007ff956b48e98 in ?? () from /usr/lib/R/lib/libR.so
#6  0x00007ff956bb56da in ?? () from /usr/lib/R/lib/libR.so
#7  0x00007ff956bba9a8 in Rf_eval () from /usr/lib/R/lib/libR.so
#8  0x00007ff956bbec39 in Rf_applyClosure () from /usr/lib/R/lib/libR.so
#9  0x00007ff956b44c38 in ?? () from /usr/lib/R/lib/libR.so
#10 0x00007ff956be80a0 in ?? () from /usr/lib/R/lib/libR.so
#11 0x00007ff956bae21a in ?? () from /usr/lib/R/lib/libR.so
#12 0x00007ff956bba9a8 in Rf_eval () from /usr/lib/R/lib/libR.so
#13 0x00007ff956bbec39 in Rf_applyClosure () from /usr/lib/R/lib/libR.so

its replicable.  not sure if this is of any interest...just trying to help.
 please ignore if uninteresting.

regards,

/iaw
----
Ivo Welch (ivo.welch@gmail.com)

	[[alternative HTML version deleted]]

On 13 July 2013 at 22:24, ivo welch wrote:
| dear R developers---I am running a pure R program on the stock binary
| debian (ubuntu) 64-bit linux distribution, 3.0.1.  for identification,
[...]
| recurse some.  I don't have symbols in my R binary, so the location may
not
| be useful, but I thought I would let you guys know.  

You can install the 'r-base-core-dbg' package [1] to get the (stripped)
debugging symbols back.

Dirk

[1] Quite generally, on Debian/Ubuntu, for package $xys the corresponding
    $xyz-dbg contains the corresponding debugging symbols.

-- 
Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com