I have a littler script which is crashing with a segmentation fault.
I tried to find out why by running it through valgrind, which produced the
output below.
I am not sure how to proceed from here (other than binary search with print
statements).
Any help would be appreciated.
Thanks,
Eric
==1258
You will much improve your chance of getting useful help if you read
and follow the posting guide (below). In particular:
1. Versions of R and packages?
2. Show us the (minimal) code that "crashes." Can you create a minimal
artificial data set that does this that we can run?
3. Are there error m
Hi! R newbie here. I wrote a script for a correlation plot, a 2d histogram
(heatmap-like) with ggplot. I've run it before with a smaller dataset and
it runs on my laptop and does what I want. Now I've extended my dataset
and R is crashing after the last line which is to generate the plot I
guess. I
On Thu, 27 Dec 2012 22:01:22 -0500
Steve Powers wrote:
Two points:
1) You don't define "crash." Did the script simply hang, did R
abruptly cease to run and exit to the OS, did the display freeze, did
the OS and machine stop working? "Crashing" is not explanatory, nor is
it descriptive of your
Steve Powers nd.edu> writes:
>
> Hello,
>
> This one has been bugging me for a long time and I have never found a
> solution. I am using R version 2.15.1 but it has come
> up in older versions of R I have used over the past 2-3 years.
>
> Q: Am I wrong to expect that R should handle hundreds
From: r-help-boun...@r-project.org [mailto:r-help-boun...@r-project.org] On
> Behalf
> Of Steve Powers
> Sent: Thursday, December 27, 2012 7:01 PM
> To: r-help@r-project.org
> Subject: [R] R crashing inconsistently within for loops
>
> Hello,
>
> This one has been bugging
Note though that the posting guide asked you not to use the word
'crash', as your audience has no idea what you mean by it. In some of
the senses people use (e.g. when R reports an error in your code), you
should expect R to 'crash'.
On 28/12/2012 09:04, Jeff Newmiller wrote:
You are not wro
You are not wrong to expect R to not crash. However, R (as most people use it)
is not monolithic, and you have provided neither reproducible code nor
sessionInfo() with the relevant packages loaded to help anyone interested in
investigating the problem. You are the most likely person to be able
Hello,
This one has been bugging me for a long time and I have never found a
solution. I am using R version 2.15.1 but it has come up in older versions of R
I have used over the past 2-3 years.
Q: Am I wrong to expect that R should handle hundreds of iterations of the
base model or statistical
> Adam Clark wrote:
>>> I'll go ahead and dig through my C code.
>> My problem was that I had a pointer (*Aest) that had less memory allocated
>> to it than I ended up storing in it ...
On Oct 31, 2012, at 9:04 AM, William Dunlap wrote:
> As long as you use C (or C++ or Fortran ...), using me
ill Dunlap
Spotfire, TIBCO Software
wdunlap tibco.com
> -Original Message-
> From: r-help-boun...@r-project.org [mailto:r-help-boun...@r-project.org] On
> Behalf
> Of Adam Clark
> Sent: Wednesday, October 31, 2012 8:47 AM
> To: Adam Clark
> Cc: r-help@r-project.org; Prof Br
Aha - got it.
My problem was that I had a pointer (*Aest) that had less memory allocated
to it than I ended up storing in it (e.g. I had *Aest = 1:100, but stored
into it values at positions 5:105). With that fixed, all works flawlessly.
Thanks a lot for the help. What I hadn't realized was that
Thanks for the advice.
I'll go ahead and dig through my C code. It's helpful to know that my C
code can cause R to crash AFTER successfully implementing the code.
I have made sure to account for C's vector indexing, and I think I'm
allocating my C memory, and passing information back and forth be
On Wed, 31 Oct 2012, Duncan Murdoch wrote:
On 12-10-30 11:13 PM, Adam Clark wrote:
I'm running R 2.15.1x64, though the same problem persists for 2.13.0x32 and
2.13.0x64.
I am trying to run compiled C code using the .C convention. The
code compiles without problems, dynamically loads within the
On 12-10-30 11:13 PM, Adam Clark wrote:
I'm running R 2.15.1x64, though the same problem persists for 2.13.0x32 and
2.13.0x64.
I am trying to run compiled C code using the .C convention. The
code compiles without problems, dynamically loads within the R
workspace with no problems, and even runs
On Oct 31, 2012, at 3:13 AM, Adam Clark wrote:
> I'm running R 2.15.1x64, though the same problem persists for 2.13.0x32 and
> 2.13.0x64.
>
> I am trying to run compiled C code using the .C convention. The
> code compiles without problems, dynamically loads within the R
> workspace with no pro
I'm running R 2.15.1x64, though the same problem persists for 2.13.0x32 and
2.13.0x64.
I am trying to run compiled C code using the .C convention. The
code compiles without problems, dynamically loads within the R
workspace with no problems, and even runs and gives correct results with
no problems
OK, now it sounds like the behavior is exactly the same for both of us. I
think Gmail sometimes gobbles up newline characters, and that must have
messed up the code I sent out before.
Someone pointed out to me that a similar problem was identified before:
https://stat.ethz.ch/pipermail/r-sig-mixe
Michael,
Good news (relatively speaking). I ran your code again, but this time
I actually looked at what I pasted in and noticed some errors. When I
actually pulled your code into a text editor, there was an issue with
one of the comments wrapping to the next line without a new #
(probably an em
t;> cat(temp)
> >>> time.rng<- temp[1]
> >>> time.nug<- temp[2]
> >>> temp<- coef(object[["space"]],unconstrained=FALSE)
> >>> space.rng<- temp[1]
> >>> space.nug<- temp[2]
> >>&g
;),function(mat)
>>> (1-time.nug)*exp(-mat/time.rng))
>>> cor.space<- lapply(attr(object[["space"]],"covariate"),function(mat)
>>> (1-space.nug)*exp(-mat/space.rng))
>>> x<- lapply(seq(length(cor.time)),function(mat)
>
("corFactor","corStruct")
>> logDet.corSPT<- getS3method("logDet","corStruct")
>> recalc.corSPT<- getS3method("recalc","corStruct")
>>
>> formula.corSPT<- function(object,...) {
>> a&l
"]],...)
}
debug(corSPT)
debug(getS3method("recalc","corSpatial"))
debug(getS3method("recalc","corStruct"))
debug(getS3method("Initialize","corSPT"))
debug(getS3method("coef<-","corSPT"))
debug(getS3method(&quo
ot;recalc","corSpatial"))
debug(getS3method("recalc","corStruct"))
debug(getS3method("Initialize","corSPT"))
debug(getS3method("coef<-","corSPT"))
debug(getS3method("coef","corSPT"))
debug(getS3method(&quo
-help-boun...@r-project.org] On Behalf Of Michael Steven
Rooney Sent: Wednesday, April 21, 2010 17:41 To: r-help@r-project.org
Subject: [R] R crashing oddly
> Hi,
>
> I am working with the package nlme, and I tried creating a new
> correlation class (which, according to the help pages,
the problem.
Uwe Ligges
nlme version is 3.1-93
The OS is Windows XP.
This is for my work computer but I get the same behavior at home using
Vista.
-- Forwarded message --
From: Sarah Goslee
Date: Wed, Apr 21, 2010 at 11:50 AM
Subject: Re: [R] R crashing oddly
To: Michael
The R version is 2.9.2.
nlme version is 3.1-93
The OS is Windows XP.
This is for my work computer but I get the same behavior at home using
Vista.
-- Forwarded message --
From: Sarah Goslee
Date: Wed, Apr 21, 2010 at 11:50 AM
Subject: Re: [R] R crashing oddly
To: Michael Steven
Hi,
I am working with the package nlme, and I tried creating a new correlation
class (which, according to the help pages, is possible if you write a few
new method functions). Anyways, I think I am 99% of the way there, but I
have a recurring problem with R crashing on seemingly innocuous statemen
Hello all,
I am using Windows XP and R 2.10.1. When using the "Open Script" or "Load
Workspace" File menu items, R tends to shut down. This does not happen while
I am writing the script within R or R is running a script. I used to have
this problem with a much earlier version of R. When I started
So here's the funny thing: I've now ran my function 5 times, and in each one
of them R crashes after I got around 20.000 distances. It could be google,
but then as soon as I quit and launch R again, I manage to get another
20.000 distances. So maybe it does have something to do with the memory
usag
On Sun, Nov 15, 2009 at 11:57 AM, Dimitri Szerman wrote:
>
> Thanks. The reason I didn't want to do something like that is because, in
> the event of a crash, I'll loose everything that was done. That's why I
> though of appending the results often.
Oops yes, I missed the 'append=TRUE' flag. Th
2009/11/15 Barry Rowlingson
> On Sun, Nov 15, 2009 at 11:10 AM, Dimitri Szerman
> wrote:
> > Hello,
> >
> > This is what I am trying to do: I wrote a little function that takes
> > addresses (coordinates) as input, and returns the road distance between
> > every two points using Google Maps. Cat
On Sun, Nov 15, 2009 at 11:10 AM, Dimitri Szerman wrote:
> Hello,
>
> This is what I am trying to do: I wrote a little function that takes
> addresses (coordinates) as input, and returns the road distance between
> every two points using Google Maps. Catch is, there are 2000 addresses, so I
> have
Hello,
This is what I am trying to do: I wrote a little function that takes
addresses (coordinates) as input, and returns the road distance between
every two points using Google Maps. Catch is, there are 2000 addresses, so I
have to get around 2x10^6 addresses. On my first go, this is what I did:
34 matches
Mail list logo
