RE: [PATCH wayland] test: remove memory leak checks

2012-08-16 Thread Eoff, Ullysses A
Ullysses A >Cc: wayland-devel@lists.freedesktop.org >Subject: Re: [PATCH wayland] test: remove memory leak checks > >On Wed, Aug 8, 2012 at 4:22 PM, U. Artie Eoff >wrote: >> From: "U. Artie Eoff" >> >> Wrapping dynamic memory functions (malloc, realloc, free,

Re: [PATCH wayland] test: remove memory leak checks

2012-08-16 Thread Kristian Høgsberg
On Wed, Aug 8, 2012 at 4:22 PM, U. Artie Eoff wrote: > From: "U. Artie Eoff" > > Wrapping dynamic memory functions (malloc, realloc, free, calloc) > can be problematic, for instance, when instrumenting code with > coverage hooks. > In general, the community consensus is to avoid writing your own

RE: [PATCH wayland] test: remove memory leak checks

2012-08-16 Thread Eoff, Ullysses A
Bump... >-Original Message- >From: Eoff, Ullysses A >Sent: Wednesday, August 08, 2012 1:22 PM >To: wayland-devel@lists.freedesktop.org >Cc: Eoff, Ullysses A >Subject: [PATCH wayland] test: remove memory leak checks > >From: "U. Artie Eoff" > >W

[PATCH wayland] test: remove memory leak checks

2012-08-08 Thread U. Artie Eoff
From: "U. Artie Eoff" Wrapping dynamic memory functions (malloc, realloc, free, calloc) can be problematic, for instance, when instrumenting code with coverage hooks. In general, the community consensus is to avoid writing your own memory leak checking and to use an existing tool such as valgrind