- prevent problems when a DB modules (like db_postgres) first calls

  db_free_row (because of some problems in the data processing), and
  then later db_free_result
- this could cause a double free, and also a crash because of null pointer
- reported from Bayan Towfiq, bayan at flowroute dot com
- fix also a similar problem in the db_free_columns function


git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@5418 689a6050-402a-0410-94f2-e92a70836424

lib/srdb1/db_res.c

@@ -85,6 +85,8 @@ inline int db_free_columns(db_res_t* _r)
 			RES_NAMES(_r)[col] = NULL;
 		}
 	}
+	RES_COL_N(_r) = 0;
+
 	/* free names and types */
 	if (RES_NAMES(_r)) {
 		LM_DBG("freeing result names at %p\n", RES_NAMES(_r));

lib/srdb1/db_row.c

@@ -90,6 +90,8 @@ inline int db_free_row(db_row_t* _r)
 				break;
 		}
 	}
+	/* now as we freed all, set number of colums to zero again */
+	ROW_N(_r) = 0;
 
 	if (ROW_VALUES(_r)) {
 		LM_DBG("freeing row values at %p\n", ROW_VALUES(_r));