search for: 80mo

Displaying 3 results from an estimated 3 matches for "80mo".

Did you mean: 80mb
2014 Dec 18
2
segfault when trying to allocate a large vector
...; double largevec[size]; memset(largevec, 0, size*sizeof(double)); return(R_NilValue); } If size if small enough (up to 10^6), everything is fine. When it reaches 10^7 as above, I get a segfault. As far as I know, a double value is represented with 8 bytes, which would make largevec above approx. 80Mo -> this is certainly large for a single variable, but should remain well below the limits of my machine... Also, doing a calloc for the same vector size leads to the same outcome. In my package, I would use large vectors that cannot be assumed to be sparse - so utilities for sparse matrices may...
2009 Jan 01
5
Samba performance issue
Hello, I sent the following message to the Debian folks. They don't think that the Debian packaging could be responsible for the issue described there. > Well, I'm not completely convinced that we will have very useful input > for you. I don't really see any reason for this to be caused by the > Debian packaging. To check this, why not compile samba from sources,
2014 Dec 18
0
segfault when trying to allocate a large vector
...ec, 0, size*sizeof(double)); > return(R_NilValue); > > } > > If size if small enough (up to 10^6), everything is fine. When it > reaches 10^7 as above, I get a segfault. As far as I know, a double > value is represented with 8 bytes, which would make largevec above > approx. 80Mo -> this is certainly large for a single variable, but > should remain well below the limits of my machine... Also, doing a > calloc for the same vector size leads to the same outcome. > > In my package, I would use large vectors that cannot be assumed to be > sparse - so utilities...