Which x? Not for 1, 10, Inf for example.
I did manage to make pf(Inf, 5, Inf) hang, but not under R-patched or
R-devel. It seems this is already fixed (please see the reporting
conditions in the FAQ or in the posting guide).
pf(Inf, n1, Inf) is the same code as pchisq(Inf, n1) and pgamma(Inf,
Full_Name: Rob Hyndman
Version: 2.1.1
OS: Windows
Submission from: (NULL) (202.7.176.132)
pf(Inf,x,Inf) causes R to hang up for any value of x.
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Milton Lopez wrote:
> I am assisting in the purchase of 64-bit Windows XP system for researchers
> who run R. These systems will have AMD Opteron processors and at least 4GB of
> RAM. I'd appreciate advice on whether there is a working version of R that
> can take full advantage of such systems.
On Tue, 31 Aug 2005, Peter Dalgaard wrote:
> Well, did you try running under a debugger?
>
> R -d gdb
>
> then "bt" after the segfault. (Make sure that things are compiled with
> -g option)
It would also be worth renaming the the function -- while I don't see
exactly how it could be causing the
I am assisting in the purchase of 64-bit Windows XP system for researchers who
run R. These systems will have AMD Opteron processors and at least 4GB of RAM.
I'd appreciate advice on whether there is a working version of R that can take
full advantage of such systems.
Milton F. López
IT Guy
In
Ricardo Luiz Andrade Abrantes <[EMAIL PROTECTED]> writes:
> Hello to everybody!
> After reading all the C code, checking for problems, and find nothing, I
> decided something a little bit different...
> If my ".so" library works in a wrog way in R it should do the same in C. So
> I created a C p
Hello to everybody!
After reading all the C code, checking for problems, and find nothing, I
decided something a little bit different...
If my ".so" library works in a wrog way in R it should do the same in C. So
I created a C program that loads my library file and the executes the same
function
I forgot to put the folowing includes in my last post:
#include
#include
Thanks,
Ricardo
-- Forwarded message --
From: Ricardo Luiz Andrade Abrantes <[EMAIL PROTECTED]>
Date: Aug 30, 2005 1:37 PM
Subject: Re: [Rd] .Call and Segmentation Fault
To: Simon Urbanek <[EMAIL PRO
On 29/ago/05, at 10:35, Prof Brian Ripley wrote:
> It does not crash for me on either Windows or Linux, but it does
> take a
> long time and the plot is a mess, so there does seem to be a
> lattice-related problem (maybe a usage one).
>
> However, I think the crash is a Mac (presumably quartz()
Gabor Grothendieck <[EMAIL PROTECTED]> wrote:
> Just to be concrete, suppose one wants to run the following as a
> concurrent process to R. (What is does is it implicitly sets x to
> zero and then for each line of stdin it adds the first field of the
> input to x and prints that to stdout unless
Hi Simon!
You are right!
Ok, here it is (a little resumed):
#include
#include
#include
#include
#include "interface.h"
SEXP main() {
int gtype, inform, m, n, maxoutit, maxtotit, maxtotfc, outiter,
totcgcnt, totfcnt, totgcnt, totiter, iprint, ncomp, i;
double f,nalpsupn,epsfeas,epsopt,snorm;
Thank you for the report.
/* */ is standard C. simpleaffy is not a CRAN package: we test those with
enough flags (-Wall -pedantic) that the use of // is flagged and would get
reported to the maintainer/submitter.
On Tue, 30 Aug 2005, Jennifer Lai wrote:
> Hi,
> After getting some help from
Hi,
After getting some help from Portland Group, I was able to pass the
initial stage of building R with Portland Group Compiler on AMD Opeteron.
For anyone who is interested in building R with PG compiler, here is a
list of set flags used in config.site,
CC=/usr/pgi/linux86-64/6.0/bin/pgcc
> You chose to report just one extremely favourable example, < ignore>
> I do think you are being `careless with the truth'.
I chose to report whatever I got and whatever I felt the result was. It was not
a scientific report and it was up to you (the R-team) to validate my result and
make further
14 matches
Mail list logo
