[GRASS-dev] [GRASS GIS] #1430: Buffer overrun in vector/diglib dig__fread_port_L with big-endian negative values on LP64 systems

GRASS GIS trac at osgeo.org
Sat Sep 28 14:20:17 PDT 2013


#1430: Buffer overrun in vector/diglib dig__fread_port_L with big-endian negative
values on LP64 systems
---------------------------------------------+------------------------------
 Reporter:  rroliver                         |       Owner:  grass-dev@…              
     Type:  defect                           |      Status:  new                      
 Priority:  normal                           |   Milestone:                           
Component:  Vector                           |     Version:  svn-trunk                
 Keywords:  diglib portable LP64 big-endian  |    Platform:  Unspecified              
      Cpu:  All                              |  
---------------------------------------------+------------------------------

Comment(by mmetz):

 Replying to [comment:4 hamish]:
 > Replying to [comment:3 mmetz]:
 > > Replying to [comment:2 hamish]:
 > > > Replying to mmetz in #2085:
 > > > > It seems that r47992 needs to be backported (see also #1430).
 > > >
 > > > ok, I guess the portable.c part of r56890 wants backporting too?
 > >
 > > Right, done in r57855,6.
 >
 > a sincere thank you, but **please** let changes to the core libraries
 prove themselves in devbr6 for a couple weeks before backporting into
 relbr64.

 Apparently, this bug appeared in the official testing environment of
 Debian with the officially included GRASS version 6.4.3 on big endian
 hardware. I guess that it will take 3 - 4 years until my change will be
 tested in the same testing environment (Debian on big endian hardware with
 GRASS version 6.4.4, yet to be released and after that to be included into
 Debian).

 We know that GRASS 7 compiles successfully on big endian hardware with AIX
 as OS. Therefore I am confident that my change will fix the reported bug.
 It would be preferable if a GRASS developer would have access to big
 endian hardware with Linux or BSD as OS and would regularly test svn
 versions of GRASS on such a system.

 Further more, I would like to see the development branch of GRASS to be
 deleted.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1430#comment:5>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list