You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Author Name: Micha Silver (@micha-silver)
Original Redmine Issue: 2303
Redmine category:grass
Assignee: Lorenzo Masini
When working in a Location with no projection information (an "X-Y" Location), you can display vector maps, but trying to display a raster causes QGIS to crash. Same results in both Linux and windows.
Recreate the issue as follows:
Using the "Create new Mapset" wizard create a new location with undefined CRS. Open a GRASS teminal and run r.mapcalc "test=1" (or equivalent in the GRASS Toolbox).
Trying to add the test raster causes the crash. Vectors display properly.
The same Location, mapset, and raster will display properly in GRASS itself - outside of QGIS.
The text was updated successfully, but these errors were encountered:
Wouldn't it be simpler to fix G_free_key_value function in GRASS to follow semantic of free() and do nothing for null pointer? The G_free in GRASS already does nothing for null pointer, as standard free() promises.
Understood, though I still suggest to apply the fix to GRASS as well. So, once new fixed version is released, messing 3rd parties code is no longer needed.
Author Name: Micha Silver (@micha-silver)
Original Redmine Issue: 2303
Redmine category:grass
Assignee: Lorenzo Masini
When working in a Location with no projection information (an "X-Y" Location), you can display vector maps, but trying to display a raster causes QGIS to crash. Same results in both Linux and windows.
Recreate the issue as follows:
Using the "Create new Mapset" wizard create a new location with undefined CRS. Open a GRASS teminal and run r.mapcalc "test=1" (or equivalent in the GRASS Toolbox).
Trying to add the test raster causes the crash. Vectors display properly.
The same Location, mapset, and raster will display properly in GRASS itself - outside of QGIS.
The text was updated successfully, but these errors were encountered: