Displaying 2 results from an estimated 2 matches for "do_dotcallgr".
Did you mean:
do_dotcall
2005 Jul 19
2
segfault with grid and null unit (PR#8014)
...portTransform + 1296
(viewport.c:356)
6 grid.so 0x060be0a0 doSetViewport + 256 (grid.c:200)
7 grid.so 0x060be5ac L_setviewport + 76 (grid.c:311)
8 libR.dylib 0x00249318 do_dotcall + 652 (dotcode.c:770)
9 libR.dylib 0x0024cc7c do_dotcallgr + 80 (dotcode.c:1450)
10 libR.dylib 0x00263b24 Rf_eval + 1536 (eval.c:405)
11 libR.dylib 0x00265b1c do_set + 224 (eval.c:1309)
2014 Apr 24
2
palette() can hang and fail due to X11
...s to the length 14
vector above, which seems like something that SHOULD be simple... Is
there some way for me to reliably do that WITHOUT invoking all this
extra X11 device machinery?
The relevant C code appears to be "palette" in
"src/library/grDevices/src/colors.c" and "do_dotcallgr" for
.Call.graphics in "src/main/dotcode.c", but I don't understand what
part is triggering the additional complex behavior, nor how I should
avoid it.
Any advice on how I should handle this robustly? (Thanks!)
--
Andrew Piskorski <atp at piskorski.com>