[GRASS5] QGIS GRASS digitizer new crash

Daniel Calvelo Aros dcalvelo at minag.gob.pe
Tue Aug 16 22:43:03 EDT 2005

From: "Maciek Sieczka" <werchowyna at epf.pl>
Sent: Wed, 17 Aug 2005 00:06:31 +0200
> Dear Developers,
> Due to some modification in Grass 6.1, which took place between 25.07.2005
> and 13.08.2005, QGIS GRASS digitizer plugin crashes in a situation 
> it used to handle fine in the past. When a vector file's datatable 
> is edited, which contains some numerical column *and* a character 
> column, and only the numerical attribute is filled by the user,
>  while the character column entry he leaves empty, QGIS crashes in a 
> following way:
> QgsGrassEdit::displayDynamic Points = 0x85bacb8 type = 0
> QgsGrassEdit::displayDynamic Points = 0 type = 0
> No DB record
> updated line = 14
> node = 27 mNodeSymb = 12
> node = 28 mNodeSymb = 12
> QObject::connect: No such signal QTabWidget::void 
> currentChanged(QWidget*) QObject::connect:  (sender name:  
>  'tabCats') QObject::connect:  (receiver name: 
> 'QgsGrassAttributesBase') Value: 14 Value: dbmi: Protocol error 
> Broken pipe
> I don't know what is the matter and if QGIS or GRASS is guilty.

Hi, Maciek. This is probably my fault, as it manifests itself in the dbf
driver, and I've been seriously tweaking that between the dates you mention.

Have you got any idea of where in the QGIS code the update is triggered? I'm
pretty sure this is a problem with interpreting an update statement. Also,
what does an empty char column stand for? NULL? 0-length string ""? That might
also be triggering unchecked insanities in the dbf driver code.


More information about the grass-dev mailing list