msdk: avoid reading data from freed memory
Both g_list_delete_link and g_list_remove remove an element and free it, so l->next is invalid (catched by valgrind) after calling g_list_delete_link or g_list_remove
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Both g_list_delete_link and g_list_remove remove an element and free it, so l->next is invalid (catched by valgrind) after calling g_list_delete_link or g_list_remove