As far as I can tell there are no out of bounds checks in "assign", so when it calls memcpy it just overrides some part of the data.table structure that it shouldn't. A simple out of bounds check would fix the issue.
On Sun, Jun 2, 2013 at 3:37 AM, Arunkumar Srinivasan <[email protected]>wrote: > Hello, > > I saw this question on SO yesterday: > http://stackoverflow.com/questions/16877027/negative-number-of-rows-in-data-table-after-incorrect-use-of-set > > I think this is a bug in "set". But unfortunately, `set` calls for c-code > internally and am not good at using gdb within R. Any ideas of what's the > problem here? > > Thanks, > Arun > > > _______________________________________________ > datatable-help mailing list > [email protected] > https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/datatable-help >
_______________________________________________ datatable-help mailing list [email protected] https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/datatable-help
