Re: [SyncEvolution] automated testing of ActiveSync
On Fr, 2011-07-08 at 18:09 +0200, Patrick Ohly wrote:
I am seeing some issues with sync key handling. In some cases, the
activesyncd debug output shows random characters. That looks very much
like an invalid memory access.
I had a brief look into eas_sync_handler_get_items(), but only found a
memory leak:
sync_key_in = g_strdup("0");
has no corresponding g_free().
The invalid memory access occurs when trying to print the new sync key
after a failure to obtain one. Potential segfault. Fix attached, also
for the g_strdup("0").
Andy, please review and apply.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
Attachments:
- eas_sync_handler_get_items.patch (text/x-patch — 754 bytes)