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 [EMAIL PROTECTED] 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, [EMAIL PROTECTED] 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 ______________________________________________ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-devel