From jerome at hivnet.ubc.ca  Mon Oct 27 18:28:05 2003
From: jerome at hivnet.ubc.ca (Jerome Asselin)
Date: Mon Oct 27 18:27:39 2003
Subject: [Rd] Segmentation fault in .Call() (PR#4761)
In-Reply-To: <Pine.LNX.4.44.0310250733450.7594-100000@gannet.stats>
References: <Pine.LNX.4.44.0310250733450.7594-100000@gannet.stats>
Message-ID: <200310271727.JAA19614@hivnet.ubc.ca>


I have reviewed the BUGS section of the FAQ. I did not realise that 
.Call() was an exception in this case.

Please accept my sincere apologies.

Jerome Asselin

On October 24, 2003 11:44 pm, Prof Brian Ripley wrote:
> Your expectations are wrong: please re-read the section on BUGS in the
> FAQ. It *starts*:
>
> If R executes an illegal instruction, or dies with an operating system
> error message that indicates a problem in the program (as opposed to
> something like "disk full"), then it is certainly a bug.  If you call
> `.C()', `.Fortran()', `.External()' or `.Call()' (or `.Internal()')
> yourself (or in a function you wrote), you can always crash R by using
> wrong argument types (modes).  This is not a bug.
>
> On Fri, 24 Oct 2003 jerome@hivnet.ubc.ca wrote:
> > Full_Name: Jerome Asselin
> > Version: 1.8.0
> > OS: RedHat Linux 7.2
> > Submission from: (NULL) (142.103.177.13)
> >
> >
> >
> > I would not expect a segmentation fault; perhaps an error message.
> >
> > > .Call("log")
> >
> > Segmentation fault
> >
> > This is always reproducable for me.
>
> So you never learn from your mistakes?
>
>
> We look forward to receiving your apologies.


[Rd] Segmentation fault in .Call() (PR#4761)
Jerome Asselin