[GRASS-dev] Re: [GRASS GIS] #1308: wingrass - dbf.exe-crash

[GRASS GIS]

#1308: wingrass - dbf.exe-crash
------------------------------+---------------------------------------------
  Reporter:  hellik           |       Owner:  grass-dev@…              
      Type:  defect           |      Status:  closed                   
  Priority:  blocker          |   Milestone:  6.4.1                    
 Component:  Default          |     Version:  svn-releasebranch64      
Resolution:  fixed            |    Keywords:  wingrass, dbf.exe, d.vect
  Platform:  MSWindows Vista  |         Cpu:  x86-32                   
------------------------------+---------------------------------------------
Changes (by hellik):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Replying to [comment:16 martinl]:
 > Replying to [comment:15 hellik]:
 > > Replying to [comment:13 martinl]:
 > > >
 > > > I found incorrect usage of `db_free_string` on variable `char *`,
 fixed in r45671. I am still unable to reproduce any crash...
 > >
 > > no chance at the moment for compiling myself r45671. I'll test it when
 nightly build will be available.
 >
 > extra build available at
 http://josef.fsv.cvut.cz/wingrass/grass64/WinGRASS-6.4.SVN-r45671-1-Setup.exe

 I've tested it a little with above build in different modes (GRASS
 6.4.SVN,GRASS 6.4.SVN with MSYS, GRASS Old TclTk GUI, GRASS Command Line
 and g.gui wxpython) with a random set of nc-sample-vectors in about 30
 sessions. I can't reproduce this anymore.

 from the dev-ML
 http://lists.osgeo.org/pipermail/grass-dev/2011-March/053825.html

 {{{
 Hi,

 2011/3/16 Markus Neteler <neteler at osgeo.org>:
 >>  it's allocated by
 >>  [source:grass/branches/releasebranch_6_4/lib/db/dbmi_base/value.c#L374
 >>  G_calloc], anyway it should be harmless, currently `G_free()` and
 >>  `db_free()` are identical.
 >
 > Ok, I was just remembering
 > http://trac.osgeo.org/grass/ticket/468#comment:2
 >
 > (were  they came from different DLLs, hence the problem)

 right, I overlooked this issue. Anyway now it should OK.

 Martin
 }}}

 I see there was some code review for this issue, therefore I'll close this
 ticket.
 please reopen if needed.

 Helmut

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/1308#comment:19>
GRASS GIS <http://grass.osgeo.org>