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

GRASS GIS trac at osgeo.org
Thu Mar 14 07:25:16 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 glynn):

 Replying to [comment:22 mmetz]:

 > I get a compiler warning for fmode.c:
 fmode.c:4:5: warning: '_fmode' redeclared without dllimport attribute:
 dllimport ignored [-Wattributes]

 FWIW, MinGW provides a /lib/binmode.o file for this purpose. Can you try:
 make FMODE_OBJ=/lib/binmode.o

 > Adding `G_gisinit()`, `G_no_gisinit()`, or "_fmode = O_BINARY", or any
 combination of these to main.c of the drivers does not help.

 If our fmode.o is wrong, it may actually prevent the run-time _fmode
 setting from working by introducing a new _fmode variable which shadows
 the real one.

 > > But rather than guess, it would be better to instrument `db__send()`
 and `db__recv()` to dump the data as hex.
 > Attached as hexdump.txt for `v.info -c map=boundary_county`. Please let
 me know if you want another format.

 Can you indicate whether the bytes are sent or received, and by which
 process? Also: where is this data coming from? `db__send` and `db__recv`?
 If so, the hexdump is even worse than the previous reports; e.g. the fifth
 entry shows something receiving 38 bytes but there is no record of it
 being sent.

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

More information about the grass-dev mailing list