can't mix g_ and non-g_ memory management

[GoogleCodeExporter]

glib lets you substitute in an alternate allocator (via
g_mem_set_vtable()), if your app wants to do something funky with memory.
Although this is not widely used, it's still considered wrong to use free()
on memory returned from g_malloc(), or g_free() on memory returned
malloc(), since they might not be equivalent. plugins/gnome.c is very
careless about this.

the patch also fixes a use of "strdup" in lib/misc.c to use px_strdup
instead, to clean up a warning

Original issue reported on code.google.com by dan.wins...@gmail.com on 6 Oct 2008 at 5:09

Attachments:

• proxy-mem.diff

[GoogleCodeExporter]

Dan,

Thank you very much for your patch.
-> Submitted as r269

Original comment by dominiqu...@gmail.com on 6 Oct 2008 at 6:14

• Changed state: Fixed