Dear R-Team, sorry for bugging (:-)), it's me again. In the FAQ coming along with the R distribution it reads: 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. This encourages me to describe a crash I encountered a few minutes ago. I had written a function in an editor, copied it to the clip-board and tried to establish it in my workspace (cut and paste). Suddenly I got the following message form Windows NT (sorry it's german): Die Anweisung "0x7762d4be" verweist auf Speicher in "0x0247c000". Der Vorgang "read" konnte nicht auf dem Speicher durchgeführt werden. Klicken Sie auf "OK um die Anwendung zu beenden. Rgui.exe-Fehler in Anwendung There are very technical terms which I hope will be translated such that it makes sense to you: The instruction "0x7762d4be" points to memory in "0x0247c000". "read" could not be carried out in memory. Click on "OK to stop the program. Clicking on OK caused R to close (and of course the most recent work was lost) --please do not edit the information below-- Version: platform = Windows arch = x86 os = Win32 system = x86, Win32 status = major = 1 minor = 0.0 year = 2000 month = February day = 29 language = R Windows NT 4.0 (build 1381) Service Pack 3 Search Path: .GlobalEnv, Autoloads, package:base Regards, *** D.Trenkler *** ==================================================================== Dietrich Trenkler (trenkler@oec.uni-osnabrueck.de) Statistik / Empirische Wirtschaftsforschung Universitaet Osnabrueck Rolandstrasse 8 Phone: +49(0) 541-969-2753 D-49069 Osnabrueck Fax : +49(0) 541-969-2745 GERMANY ==================================================================== -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-devel-request@stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
R-crash using cut-and-paste (PR#472)
3 messages · Trenkler, Dietrich, Brian Ripley, Uwe Ligges
On Tue, 7 Mar 2000 dtrenkler@nts6.oec.uni-osnabrueck.de wrote:
Dear R-Team, sorry for bugging (:-)), it's me again. In the FAQ coming along with the R distribution it reads: 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. This encourages me to describe a crash I encountered a few minutes ago. I had written a function in an editor, copied it to the clip-board and tried to establish it in my workspace (cut and paste). Suddenly I got the following message form Windows NT (sorry it's german):
[...] How big was the function you were trying to paste in? There are distinct limits to such cut-and-paste, not all of which are under our control. To quote more of the FAQ: Please include an example that reproduces the problem, preferably the simplest one you have found. Without such an example, there is nothing we can do to help. As a general work-around, you will find it much easier to use source() to load in sizeable functions than cut-and-paste.
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 272860 (secr) Oxford OX1 3TG, UK Fax: +44 1865 272595 -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-devel-request@stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
Hi! Prof Brian D Ripley schrieb:
On Tue, 7 Mar 2000 dtrenkler@nts6.oec.uni-osnabrueck.de wrote:
Dear R-Team, sorry for bugging (:-)), it's me again. In the FAQ coming along with the R distribution it reads: 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. This encourages me to describe a crash I encountered a few minutes ago. I had written a function in an editor, copied it to the clip-board and tried to establish it in my workspace (cut and paste). Suddenly I got the following message form Windows NT (sorry it's german):
... Happens here too (R 1.0.0, Windows NT 4.0, SP5). Sometimes with Dr. Watson, sometimes as described above by D.Trenkler, sometimes R terminates without any message.
How big was the function you were trying to paste in? There are distinct limits to such cut-and-paste, not all of which are under our control. To quote more of the FAQ: Please include an example that reproduces the problem, preferably the simplest one you have found. Without such an example, there is nothing we can do to help.
If you paste the following function about four times (makes no sense,
but reproduces the error without pasting a really big function), the
error occurs:
-------------
"scoredach" <-
function (x)
{
v1 <- x[1]
u11<- x[2]
u12<- x[3]
v2 <- x[4]
u21<- x[5]
u22<- x[6]
v3 <- x[7]
u31<- x[8]
u32<- x[9]
w1 <- x[10]
w2 <- x[11]
w3 <- x[12]
z11<- x[13]
z21<- x[14]
z31<- x[15]
z12<- x[16]
z22<- x[17]
z32<- x[18]
scoredach <- v1/(1 + exp(-(u11 * xseq + u12 * yseq)))
+ v2/(1 + exp(-(u21 * xseq + u22 * yseq)))
+ v3/(1 + exp(-(u31 * xseq + u32 * yseq)))
return(scoredach)}
---------------------
As a general work-around, you will find it much easier to use source() to load in sizeable functions than cut-and-paste.
Regards, Uwe Ligges -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-devel-request@stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._