gatt: proximity: Fix mismatching allocation and deallocation 71/134271/1
authorSyam Sidhardhan <s.syam@samsung.com>
Thu, 15 Jun 2017 14:27:19 +0000 (19:57 +0530)
committerSyam Sidhardhan <s.syam@samsung.com>
Thu, 15 Jun 2017 14:32:06 +0000 (20:02 +0530)
commit1f3cd04b435d5748ca9d2ae8c649bf50b7b32748
tree39b3f470a246b6a57b49f626b8ac9ff3fbd60bf8
parent948e3dec1c24d098f5b33c1e53c63b3f5ef132d8
gatt: proximity: Fix mismatching allocation and deallocation

As per the glib documentation, the memory allocated using the glib
api's needs to be freed using corresponding glib free api's and not
libc api's, otherwise undefined behaviour can happen. This is because
the libc allocation and glib allocation uses different memory pools.
Similarly for libc api's.

Change-Id: I502ca5f143417c2ce4acf12e47b317d5339a48c1
Signed-off-by: Syam Sidhardhan <s.syam@samsung.com>
src/bluetooth-gatt.c
src/bluetooth-proximity.c