> Emil Bodeon Fri, 14 Sep 2018 13:04:29 + writes:
> I found some strange behaviour, which I think is a bug.
> Could someone make an account for me on Bugzilla or
> pass on my report?
I did create a bugzilla account for you (you should've got the
automatic e-mail in the me
Thanks to you both -- I see it now on Ubuntu. A typo in the code for
restoring the SIGINT handler in the timeout cleanup was installing the
wrong handler. Fixed in R-devel and R-patched.
Best,
luke
On Fri, 14 Sep 2018, Kevin Ushey wrote:
FWIW I can reproduce on macOS with R 3.5.1. A smaller e
FWIW I can reproduce on macOS with R 3.5.1. A smaller example:
system2("ls", timeout = 5); x <- sample(1:1E8)
If I try to interrupt R while that sample call is running, R itself is closed.
Best,
Kevin
On Fri, Sep 14, 2018 at 10:53 AM Emil Bode wrote:
>
> I hope it's not too specific in my
I hope it's not too specific in my setup...
I've tried with system2 added on the first line, so:
Example.R:
system2('ls', timeout=5)
cat('Start non-interruptable functions\n')
sample_a <- sample(1:1e7)
sample_b <- sample(1:2e7)
matching <- match(sample_a, sample_b)
cat('Finished\n')
Sys.sleep(10)
I can't reproduce this. Can you be more precise: exactly where are you
putting the system2 call and exactly where are you sending the
interrupt signal with ^C?
Best,
luke
On Fri, 14 Sep 2018, Emil Bode wrote:
Hi all,
I found some strange behaviour, which I think is a bug. Could someone make
Hi all,
I found some strange behaviour, which I think is a bug. Could someone make an
account for me on Bugzilla or pass on my report?
The problem:
When pressing Ctrl-C when a file is sourced in R, run from Terminal (macOS),
sometimes the entire session is ended right away, while I just want to
