From ripley at stats.ox.ac.uk  Sat Oct 25 08:44:19 2003
From: ripley at stats.ox.ac.uk (Prof Brian Ripley)
Date: Sat Oct 25 08:43:25 2003
Subject: [Rd] Segmentation fault in .Call() (PR#4761)
In-Reply-To: <200310242130.h9OLUS0P016175@pubhealth.ku.dk>
Message-ID: <Pine.LNX.4.44.0310250733450.7594-100000@gannet.stats>

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.

-- 
Brian D. Ripley,                  ripley@stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595


[Rd] Segmentation fault in .Call() (PR#4761)
Prof Brian Ripley