search for: 5786104

Hello everybody, I'm running R 1.8.1 on both Linux and OS X compiled with gcc 3.2.2 and 3.3, respectively. The following call seems to freeze the interpreter on both systems: > chisq.test(matrix(c(233, 580104, 3776, 5786104), 2, 2), simulate.p.value=TRUE) By freeze, I mean, the function call never returns (running > 10 hours so far), the process is unresponsive to SIGINT (but I call kill it with TERM), and the process still consumes cycles on the CPU. Browsing through the code, it seems to be getting stuck on...

On Thu, 11 Dec 2003, Jeffrey Chang wrote: > Hello everybody, > > I'm running R 1.8.1 on both Linux and OS X compiled with gcc 3.2.2 and > 3.3, respectively. The following call seems to freeze the interpreter > on both systems: > > chisq.test(matrix(c(233, 580104, 3776, 5786104), 2, 2), > simulate.p.value=TRUE) > > By freeze, I mean, the function call never returns (running > 10 hours > so far), the process is unresponsive to SIGINT (but I call kill it with > TERM), and the process still consumes cycles on the CPU. > This is due to calling `exp'...

...>> Hello everybody, >> >> I'm running R 1.8.1 on both Linux and OS X compiled with >> gcc 3.2.2 and 3.3, respectively. The following call >> seems to freeze the interpreter on both systems: > >> chisq.test(matrix(c(233, 580104, 3776, 5786104), 2, 2), >> simulate.p.value=TRUE) >> >> By freeze, I mean, the function call never returns >> (running > 10 hours so far), the process is unresponsive >> to SIGINT (but I call kill it with TERM), and the process >> still consumes cycl...

...ybody, >>> >>> I'm running R 1.8.1 on both Linux and OS X compiled with >>> gcc 3.2.2 and 3.3, respectively. The following call >>> seems to freeze the interpreter on both systems: > >>> chisq.test(matrix(c(233, 580104, 3776, 5786104), 2, 2), >>> simulate.p.value=TRUE) >>> >>> By freeze, I mean, the function call never returns >>> (running > 10 hours so far), the process is unresponsive >>> to SIGINT (but I call kill it with TERM), and the >>> pro...