Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-19 Thread Ben Goodrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: r-base-core Version: 2.5.1-2 Severity: important Hi Dirk, To replicate this problem on a amd64 machine, do cd /tmp echo "log(1)" > crash.R R -d "valgrind --verbose --db-attach=yes" --vanilla < crash.R The last line is adapted from http://

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-20 Thread Dirk Eddelbuettel
Hi Ben, Thanks for the bug report. On 20 August 2007 at 01:48, Ben Goodrich wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Package: r-base-core | Version: 2.5.1-2 | Severity: important | | Hi Dirk, | | To replicate this problem on a amd64 machine, do | | cd /tmp | echo "log(1)"

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-20 Thread Douglas Bates
I have been able to run the development version of R with valgrind on an Ubuntu (gutsy) amd64 system. I am compiling R with the 4.2.1 series of the gcc compilers. [EMAIL PROTECTED]:~$ R-2.6 --version R version 2.6.0 Under development (unstable) (2007-08-20 r42573) Copyright (C) 2007 The R Founda

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-20 Thread Dirk Eddelbuettel
Doug, On 20 August 2007 at 11:12, Douglas Bates wrote: | I have been able to run the development version of R with valgrind on | an Ubuntu (gutsy) amd64 system. I am compiling R with the 4.2.1 | series of the gcc compilers. Thanks for that. Ben, how does your system differ? Dirk -- Three o

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-20 Thread Ben Goodrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, Dirk Eddelbuettel wrote: > Doug, > > On 20 August 2007 at 11:12, Douglas Bates wrote: > | I have been able to run the development version of R with valgrind on > | an Ubuntu (gutsy) amd64 system. I am compiling R with the 4.2.1 > | series o

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-20 Thread Dirk Eddelbuettel
On 20 August 2007 at 22:04, Ben Goodrich wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Hi all, | | Dirk Eddelbuettel wrote: | > Doug, | > | > On 20 August 2007 at 11:12, Douglas Bates wrote: | > | I have been able to run the development version of R with valgrind on | > | an Ubun

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-20 Thread Ben Goodrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dirk Eddelbuettel wrote: > Could be the compiler, could be R. FWIW the debian/rules specifies gcc 4.2 > as per > > > # edd 03 Apr 2006 switch to gfortran > # edd 04 Apr 2006 use optimflags, build per-compiler flags later > # edd 26 Jun 2007 need

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-21 Thread Johannes Ranke
> | > | I noticed this problem with R 2.5.1 (binary from Debian unstable or > | source from CRAN); do you want me to try the SVN version of R? > > Could be the compiler, could be R. FWIW the debian/rules specifies gcc 4.2 > as per > > > # edd 03 Apr 2006 switch to gfortran > # edd 04 Apr 2006

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-21 Thread Ben Goodrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Johannes Ranke wrote: >> | >> | I noticed this problem with R 2.5.1 (binary from Debian unstable or >> | source from CRAN); do you want me to try the SVN version of R? >> >> Could be the compiler, could be R. FWIW the debian/rules specifies gcc 4.2 >

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-21 Thread Johannes Ranke
* Ben Goodrich <[EMAIL PROTECTED]> [070821 16:00]: > Johannes Ranke wrote: > >> | > >> | I noticed this problem with R 2.5.1 (binary from Debian unstable or > >> | source from CRAN); do you want me to try the SVN version of R? > >> > >> Could be the compiler, could be R. FWIW the debian/rules spe

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-21 Thread Dirk Eddelbuettel
On 21 August 2007 at 09:37, Ben Goodrich wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Johannes Ranke wrote: | >> | | >> | I noticed this problem with R 2.5.1 (binary from Debian unstable or | >> | source from CRAN); do you want me to try the SVN version of R? | >> | >> Could be t

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-21 Thread Ben Goodrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dirk Eddelbuettel wrote: > I still have the feeling that I am not quite sure why and where this would be > a bug in R. As Doug demonstrated, it works merrily on amd64 with the same > toolchain. > > So the ball is back in your court as we're not quit

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-21 Thread Dirk Eddelbuettel
On 21 August 2007 at 11:34, Ben Goodrich wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Dirk Eddelbuettel wrote: | > I still have the feeling that I am not quite sure why and where this would be | > a bug in R. As Doug demonstrated, it works merrily on amd64 with the same | > tool

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-21 Thread Peter Dalgaard
Dirk & folks, Could you please cut me from the Cc:? This is the twelfth entry in my inbox, I'm leaving for Lisbon tomorrow, and I'm unlikely to dive into this issue in the immediate future. -pd Dirk Eddelbuettel wrote: On 21 August 2007 at 11:34, Ben Goodrich wrote: | -BEGIN PGP SIGN

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-24 Thread Dirk Eddelbuettel
On 21 August 2007 at 14:23, Dirk Eddelbuettel wrote: | ld-2.6.1 reminds me -- this may be a library issue. I think we just jumped | from libc6 2.4 to 2.6, and not all compilers may be aligned. Just a random | thought though. I was bitten by a similar issue today when R, PostgreSQL and PL/R didn

Bug#438823: r-base-core: valgrind throws an error when R starts on amd64

2007-08-25 Thread Ben Goodrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Dirk, I suggest this bug report be closed. Today I dist-upgraded (for the first time in about a week) within unstable and it pulled in the newest valgrind from two days ago, and the original crash is gone on amd64 (not entirely sure why from readin