[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
memory allocation clarification
From: |
Chris Brannon |
Subject: |
memory allocation clarification |
Date: |
Sat, 20 Feb 2010 09:58:16 -0600 |
Jose Vilmar Estacio de Souza wrote:
> The example you gave in src/modules/module_utils.c was what caught my
> attention.
> I was investigating a problem with the sd_ibmtts and I came across this
> situation.
Hi Jose,
Yes, I noticed your comment about that in IRC yesterday.
> What I did as an experiment, was to replace in the routines xmalloc and
> xfree the calls malloc and free for g_malloc and g_free.
Great! Do you have a patch?
The modules which use functions from module_utils.c also need to change,
and I can do that.
> Are you trying to fix these problems?
I am.
> BTW, the problem that I am facing with sd_ibmtts, is that sometimes it
> receives a SIGSEGV. The problem happens in different routines.
Can you tell me what those routines are?
-- Chris
- [PATCH] Corrected some memory leacs in src/tests/run_test.c, (continued)
- [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, 2010/02/17
- 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 <=
- 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