[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
memory allocation clarification
From: |
Luke Yelavich |
Subject: |
memory allocation clarification |
Date: |
Thu, 18 Feb 2010 12:07:28 +1100 |
On Thu, Feb 18, 2010 at 11:58:35AM EST, jose vilmar estacio de souza wrote:
> It's important to match |g_malloc()|
> <http://library.gnome.org/devel/glib/unstable/glib-Memory-Allocation.html#g-malloc>
> with |g_free()|
> <http://library.gnome.org/devel/glib/unstable/glib-Memory-Allocation.html#g-free>,
> plain |malloc()| with |free()|, and (if you're using C++) new with
> delete and new[] with delete[]. Otherwise bad things can happen,
> since these allocators may use different memory pools (and
> new/delete call constructors and destructors).
>
> Am I missing something?
This sounds correct. I believe one of Chris' recent patches for
speech-dispatcher corrected such an issue.
Luke
- [PATCH] Corrected some memory leacs in src/tests/run_test.c, Rui Batista, 2010/02/16
- [PATCH] Corrected some memory leacs in src/tests/run_test.c, Chris Brannon, 2010/02/16
- [PATCH] Corrected some memory leacs in src/tests/run_test.c, Rui Batista, 2010/02/16
- [PATCH] Corrected some memory leacs in src/tests/run_test.c, Rui Batista, 2010/02/16
- [PATCH] Corrected some memory leacs in src/tests/run_test.c, Rui Batista, 2010/02/16
- memory allocation clarification, jose vilmar estacio de souza, 2010/02/17
- memory allocation clarification,
Luke Yelavich <=
- memory allocation clarification, jose vilmar estacio de souza, 2010/02/18
- memory allocation clarification, Chris Brannon, 2010/02/19
- memory allocation clarification, jose vilmar estacio de souza, 2010/02/20
- memory allocation clarification, Chris Brannon, 2010/02/20
- memory allocation clarification, jose vilmar estacio de souza, 2010/02/20
- memory allocation clarification, Chris Brannon, 2010/02/22
- memory allocation clarification, jose vilmar estacio de souza, 2010/02/22