<div>Mike,</div>
<div> </div>
<div> It was understood. I want to know anyone in the mail list have good tools to debug this memory leakage issues. I was using the dmalloc. but after changing the configure file to use the arm crosscompile option, I got some werid errors about the dmalloc.h</div>
<div> /pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -g -O2 -DHAVE_STDARG_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_MMAN_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_W32API_WINBASE_H=0 -DHAVE_W32API_WINDEF_H=0 -DHAVE_SYS_CYGWIN_H=0 -DHAVE_SIGNAL_H=1 -I. -I. -c arg_check.c -o ./arg_check.o<br>
In file included from arg_check.c:40:<br>dmalloc.h:460: error: parse error before "__extension__"<br>dmalloc.h:460: error: `__len' undeclared here (not in a function)<br>dmalloc.h:460: error: initializer element is not constant<br>
dmalloc.h:460: error: parse error before "if"<br>dmalloc.h:460: error: conflicting types for '__retval'<br>dmalloc.h:460: error: previous definition of '__retval' was here<br>dmalloc.h:460: warning: data definition has no type or storage class<br>
dmalloc.h:460: error: parse error before '}' token<br><br>Regards,</div>
<div> </div>
<div>Yihe<br></div>
<div class="gmail_quote">On Tue, Feb 17, 2009 at 12:57 PM, Michael Smith <span dir="ltr"><<a href="mailto:msmith@xiph.org">msmith@xiph.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">On Tue, Feb 17, 2009 at 10:49 AM, yihe <<a href="mailto:tihpa2004@gmail.com">tihpa2004@gmail.com</a>> wrote:<br>> Mike,<br>><br>> I am a new hand to linux/gstreamer.<br>> The project is to let the system to decoder multples mepg2 avi.stream on the<br>
> hardware and mux the decoded buffers to a single display buffer and display<br>> out.<br>><br>> our team has developed the decoder element and display element based on the<br>> hardware platform.<br>> My job is to make a muxer element between these two elements,besides that,<br>
> filesrc and avimux elemetn were used in the pipeline.<br>><br>> I guess somehow the project has some memory leakage. since the oom-kiill did<br>> not occur at first running. it was only present after nth running n,where n<br>
> was decided by the number of input streams.<br><br></div>Ok, that's entirely possible. We're not familiar with your system<br>though, and you're using a bunch of your own plugins - so we can't<br>really help you with any of that sort of thing.<br>
<br>Good luck!<br><br>Mike<br></blockquote></div><br>