Hi Dirk,
Thanks for the report. ?Doug has pointed out a few times that the 'thread-safe malloc' (libtcmalloc) from the Google Performance Tools manages to tickle some memory bug too, coupled with an R-dev build with proper flags. ?Unfortunately I was unable to reproduce that on my box. ?If this leads to anything we may well get a chance to chase this down.
Thanks for the reply. Like I said, it also works perfectly on most of my systems. *Just to correct my initial mail: The problem occurs with 32-bit R on 64-bit Windows 7.* I don't think that it's only my machine, since the checks on win-builder also threw an error when I submitted my package (it could not run the examples). - Andreas
Andreas Alfons Faculty of Business and Economics, KU Leuven www.econ.kuleuven.be/andreas.alfons/public/