search for: tcltk_unix

...[.. snip ..] building package 'tcltk' mkdir ../../../library/tcltk mkdir ../../../library/tcltk/R mkdir ../../../library/tcltk/demo mkdir ../../../library/tcltk/exec mkdir ../../../library/tcltk/po mkdir ../../../library/tcltk/man making init.d from init.c making tcltk.d from tcltk.c making tcltk_unix.d from tcltk_unix.c `Makedeps' is up to date. gcc -std=gnu99 -I../../../../include -I/usr/local/include/tcl8.4 -I/usr/local/include/tk8.4 -I/usr/local/include -I/usr/local/include -fpic -g -O2 -c init.c -o init.o gcc -std=gnu99 -I../../../../include -I/usr/local/include/tcl8.4 -I/usr/local/...

...erial = 15621, send_event = 1, ...(snip)... , 268686226}}) at devX11.c:627 #2 0xb796296c in R_ProcessX11Events (data=0x0) at devX11.c:665 #3 0x080fd99c in R_runHandlers (handlers=0x8263d28, readMask=0x82cf6a0) at sys-std.c:363 #4 0xb74e159e in RTcl_eventProc (evPtr=0x97dfbf0, flags=-1) at tcltk_unix.c:136 #5 0xb749d6a3 in Tcl_ServiceEvent () from /usr/lib/libtcl8.4.so.0 #6 0xb749da32 in Tcl_DoOneEvent () from /usr/lib/libtcl8.4.so.0 #7 0xb74e14ee in TclSpinLoop (data=0x0) at tcltk_unix.c:60 #8 0x0814d4a6 in R_ToplevelExec (fun=0xb74e14d0 <TclSpinLoop>, data=0x0) at context.c:604 #9...

When using multicore-forking of the parallel package, is it possible for a child process to know that it is a fork? Something like: parallel::mclapply(1:10, FUN = function(i) { test_if_running_in_a_fork() }) I'm looking into ways to protect against further parallel processes (including threads), which not necessarily are created via the parallel:mc* API, are being spawned off recursively.

Dear list, It seems that something changed between R 4.2.3 and R 4.3 (tested with 4.3.2) that broke the Tcl socket server. Here is a reproducible example: - R process #1 (Tcl socket server): library(tcltk) cmd <- r"( proc accept {chan addr port} { ;# Make a proc to accept connections puts "$addr:$port says [gets $chan]" ;# Receive a string puts $chan goodbye