v.info: Fix Resource Leak Issues

[ShubhamDesai]

This pull request fixes issue identified by Coverity Scan (CID : 1415719)
Used G_free() to fix this issue.

[nilason]

Please address all similar issues in v.info (filter with /vector/v.info/*.c ).

[ShubhamDesai]

Please address all similar issues in v.info (filter with /vector/v.info/*.c ).

Done. Addressed all issues.
CID : 1207862, 1207863, 1207864, 1207865 ,1207866, 1207867, 1207868, 1207869, 1415621, 1415654, 1415719, 1415731, 1415761 ,1415807)

[nilason]

Looks good, just a minor observation.

[nilason]

Great, thanks!

[nilason]

Now I see what is wrong. Vect_get_proj_name(), only sometimes return an allocated string (in contradiction to its documentation). Sometimes it returns constants. If you skip the freeing of the result here, we're good to go.

(You're more than welcome to fix Vect_get_proj_name to always return an allocated string in another PR.

grass/lib/vector/Vlib/header.c

Line 536 in 7c426cb

const char *Vect_get_proj_name(struct Map_info *Map)

)

[ShubhamDesai]

Now I see what is wrong. Vect_get_proj_name(), only sometimes return an allocated string (in contradiction to its documentation). Sometimes it returns constants. If you skip the freeing of the result here, we're good to go.

(You're more than welcome to fix Vect_get_proj_name to always return an allocated string in another PR.

grass/lib/vector/Vlib/header.c

Line 536 in 7c426cb

const char *Vect_get_proj_name(struct Map_info *Map)

)

I have removed it temporarily. I will create new PR to fix the function Vect_get_proj_name