Saptarshi, if you look at the sheer number of shared libraries involved, heap corruption may have happened due to errors in any of these. Finding the reason for such problems is usually difficult, but almost impossible without a reproducible example. If you could boil it down to a minimal example still triggering the access violation, one could try to run it under control of a memory guard like valgrind.
Best Hugo On Friday 24 June 2011 17:12:26 Saptarshi Guha wrote: > Hello, > > I'm trying to use rjson to parse a JSON object. The object can be found here > > http://pastebin.com/np0s5hgM > > (you'll probably need to add quotes around the content) > > > fromJSON returns the error > glibc detected home/sguha/lib64/R/bin/exec/R: realloc(): invalid next > size: 0x000000000209e210 *** > > Is there a fix coming soon? Maybe CRAN should also have an outstanding > bug field - packages with unfixed bugs could be removed. > > > Cheers > Joy > > > rjson- 0.2.3 > and > > R.version > _ > platform x86_64-unknown-linux-gnu > arch x86_64 > os linux-gnu > system x86_64, linux-gnu > status > major 2 > minor 13.0 > year 2011 > month 04 > day 13 > svn rev 55427 > language R > version.string R version 2.13.0 (2011-04-13) > > ______________________________________________ > R-help@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code. ______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.