[GRASS-dev] [GRASS GIS] #1866: broken db driver communication in winGRASS 7

GRASS GIS trac at osgeo.org
Mon Mar 11 17:52:59 PDT 2013


#1866: broken db driver communication in winGRASS 7
------------------------------+---------------------------------------------
 Reporter:  martinl           |       Owner:  grass-dev@…              
     Type:  defect            |      Status:  new                      
 Priority:  blocker           |   Milestone:  7.0.0                    
Component:  Database          |     Version:  unspecified              
 Keywords:  sqlite, wingrass  |    Platform:  MSWindows 2K             
      Cpu:  Unspecified       |  
------------------------------+---------------------------------------------

Comment(by mmetz):

 Replying to [comment:12 mmetz]:
 > Replying to [comment:11 cmbarton]:
 > > This seems to be working fine on the Mac for R55039. I just did
 db.describe for forestations in the nc_spm_08 demo set for data in sqlite.
 No problem.
 >
 > The drivers are working just fine. Someone is not listening properly,
 i.e. the dblib as used by modules, because the drivers are sending correct
 information, but the dblib receives bargage. There are some parts in the
 code, in the db lib, in gislib for spawning and in the wxGUI that have
 switches for Windows. But the relevant code in the db drivers, the db lib
 and gislib is identical between 6.4, 6.5 and 7. The only differences I
 could find between trunk and devbr6/relbr64 are in the GRASS startup
 script and in the wxGUI. Is it possible that the wxGUI or the startup
 script are highjacking file descriptors of the pipes?

 The db driver communication was broken with r53257, September 2012. For
 some unknown reason, wingrass needs to be linked against -lxdr, even
 though all references to the xdr lib should have been eliminated. Fixed in
 r55332, but this ticket should not be closed until the ultimate reason is
 known.

 Markus M

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



More information about the grass-dev mailing list