What Peter & Vladimir refers to are the causes of problems - adding
"-Wall" to all of CFLAGS, CXXFLAGS, FFLAGS should spot some of them.
I did know of one case of uninitialised variable causing a crash -
doing "FILE *file; close(file);" crashes with gcc but not with sun
workshop (sun workshop imp
The problem with the misuse of 'long' in package 'subselect' was reported
to Mr Cadima in February 2005 (along with a number of other package
maintainers).
On Fri, 5 Jan 2007, Vladimir Dergachev wrote:
> On Friday 05 January 2007 12:10 pm, Peter Dalgaard wrote:
>> Hin-Tak Leung wrote:
>>> I go
On Friday 05 January 2007 12:10 pm, Peter Dalgaard wrote:
> Hin-Tak Leung wrote:
> > I got the same error with 64-bit R 2.4.1 on FC6 x86_64, and 32-bit
> > R 2.4.1 on the same machine is okay. There is definitely something wrong
> > with your code.
> >
> > I would suggest fixing all the compier war
Hin-Tak Leung wrote:
> I got the same error with 64-bit R 2.4.1 on FC6 x86_64, and 32-bit
> R 2.4.1 on the same machine is okay. There is definitely something wrong
> with your code.
>
> I would suggest fixing all the compier warnings - there are piles of
> them about uninitialized variables, and a
I got the same error with 64-bit R 2.4.1 on FC6 x86_64, and 32-bit
R 2.4.1 on the same machine is okay. There is definitely something wrong
with your code.
I would suggest fixing all the compier warnings - there are piles of
them about uninitialized variables, and about doing comparison
between si
Hello,
I would appreciate *any* ideas on this problem. I'm the maintainer of a
package ("subselect"), which on CRAN's Daily Package Checks is OK on all
flavours of R, except r-devel Linux x86_64, where there is a "memory not
mapped" segfault with the very first example that is tried out (outp
