Skip to content

(PR#11281) Bug in R 2.7 for over long lines (crasher+proposed fix!)

3 messages · Martin Maechler, Antonio, Fabio Di Narzo, Roger Bivand

Original
Martin Maechler
# 
BDR> This example does not crash in R 2.7.0, R-patched nor
    BDR> R-devel (r45677) for me (x86_64 F8 Linux.)  It also
    BDR> does not crash with the CRAN build of R 2.7.0 on
    BDR> Windows XP.

Neither does it for me in R 2.7.0 
on two x86_64 Linux platforms:  
   Ubuntu 8.04 and Redhat Enterprise 5.1

Martin
BDR> On Tue, 13 May 2008, Soeren Sonnenburg wrote:
>> On Mon, 2008-05-12 at 11:10 +0200,
>> maechler at stat.math.ethz.ch wrote:
>>> Hi Soeren,
    >>>>>>>> "SS" == Soeren Sonnenburg <bugreports at nn7.de> on
    >>>>>>>> Sat, 10 May 2008 05:32:14 +0000 writes:
    >>>
SS> On Sat, 2008-04-26 at 09:38 +0200, Peter Dalgaard wrote:
>>> >> bugreports at nn7.de wrote: > OK, I am just sending it
    >>> here >> too as it looks like r-devel at r-project.org > is
    >>> not the >> right place:
    >>> >>>
    >>> >> I think it was seen there too, just that noone got
    >>> around >> to reply. In R-bugs, there's a filing system
    >>> so that it >> won't be completely forgotten...
    >>> 
    SS> Looks like no one cares about this :(
    >>> 
    >>> Just "looks like" but it aint...
    >>> 
    SS> What should I do now? I mean I pointed directly to the
    SS> bug and did show how it could be fixed....
    >>> 
    >>> I'm not among the parse experts within R-core, but I
    >>> think the main problem with your report is that you talk
    >>> about a crash but do not provide "self-contained
    >>> reproducible" code to produce such a crash, but just the
    >>> assertion that you get crashes when working on R <->
    >>> Swig interaction.  Can you construct simple R code
    >>> producing the crash?
    >> 
    >> No. I put however difficult autogenerated (~800k big!) .R
    >> code that will crash R 2.7 at
    >> http://nn7.de/debugging/Features.R for everyone to enjoy
    >> :)
    >> 
    >> Sourcing it will crash R2.7.0 (without my fix) but not
    >> 2.8.
    >> 
    >> Soeren
    >> 
    >> ______________________________________________
    >> R-devel at r-project.org mailing list
    >> https://stat.ethz.ch/mailman/listinfo/r-devel
    >>
Antonio, Fabio Di Narzo
# 
2008/5/13  <maechler at stat.math.ethz.ch>:
I get a segfault.
R version 2.7.0 (2008-04-22)
i686-pc-linux-gnu

locale:
LC_CTYPE=it_IT.UTF-8;LC_NUMERIC=C;LC_TIME=it_IT.UTF-8;LC_COLLATE=it_IT.UTF-8;LC_MONETARY=C;LC_MESSAGES=it_IT.UTF-8;LC_PAPER=it_IT.UTF-8;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=it_IT.UTF-8;LC_IDENTIFICATION=C

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

$ uname -r
2.6.22-14-generic

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Roger Bivand
    

    

      
      #
    

  


  

      
On Tue, 13 May 2008, maechler at stat.math.ethz.ch wrote:

        

            

      
      
      
    

        
For the record, it does crash release 2.7.0 on a fully updated RHEL 5 
ix86, on fully updated F7 ix86 (gdb "memory corruption"); on RHEL 4 ix86 
gdb says: "double free or corruption" and points at

#0  0x003bc7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x00baa815 in raise () from /lib/tls/libc.so.6
#2  0x00bac279 in abort () from /lib/tls/libc.so.6
#3  0x00bdecca in __libc_message () from /lib/tls/libc.so.6
#4  0x00be555f in _int_free () from /lib/tls/libc.so.6
#5  0x00be593a in free () from /lib/tls/libc.so.6
#6  0x08169131 in Rf_yyparse () at gram.c:3041
#7  0x08169284 in R_Parse1 (status=0x0) at gram.c:3326
#8  0x08169362 in R_Parse (n=-1, status=0xbfffe9d8, srcfile=0x8b33820)
     at gram.c:3447

This is of course only of historical interest, since 2.8.0 (2008-05-13 
r45678) on RHEL 4 completes source("Features.R") repeatedly with no 
apparent difficulty. So it was a 32-bit problem on some Linux systems.

Roger