Martin Morgan
2012-Sep-24 23:42 UTC
[Rd] Segmentation fault when options(max.print = .Machine$integer.max)
Seemed like a good idea at the time, but > options(max.print = .Machine$integer.max) > 1:10 [1] Program received signal SIGSEGV, Segmentation fault. because of an integer overflow at src/main/printvector.c:176 > sessionInfo() R Under development (unstable) (2012-09-24 r60800) Platform: x86_64-unknown-linux-gnu (64-bit) ... also R-patched, etc. Martin -- Computational Biology / Fred Hutchinson Cancer Research Center 1100 Fairview Ave. N. PO Box 19024 Seattle, WA 98109 Location: Arnold Building M1 B861 Phone: (206) 667-2793
Martin Maechler
2012-Sep-25 12:26 UTC
[Rd] Segmentation fault when options(max.print = .Machine$integer.max)
> Seemed like a good idea at the time,I'm curious. Why is it (setting max.print much too large) a good idea?> but > > options(max.print = .Machine$integer.max) > > 1:10 > [1] > Program received signal SIGSEGV, Segmentation fault.> because of an integer overflow at src/main/printvector.c:176> > sessionInfo() > R Under development (unstable) (2012-09-24 r60800) > Platform: x86_64-unknown-linux-gnu (64-bit) > ...> also R-patched, etc.Thank you, Martin. I'm about to commit fixes for this. "another" Martin.> Martin > -- > Computational Biology / Fred Hutchinson Cancer Research Center > 1100 Fairview Ave. N. > PO Box 19024 Seattle, WA 98109
Possibly Parallel Threads
- You are right and the problem is solved. Re: about the possible errors in Rgraphviz Package
- You are right and the problem is solved. Re: about the possible errors in Rgraphviz Package
- Issues with libcurl + HTTP status codes (eg. 403, 404)
- Make as.factor an S3 generic?
- S4 method dispatch sometimes leads to incorrect when object loaded from file?