After the third Malloc Bug today I have started the backend in a terminal with the following command:<br><br>MALLOC_CHECK_=3 mythbackend<br><br>Will report back with result when it occurs next<br><br>t.dennis<br><br><br><br>
<div class="gmail_quote">On Sun, Feb 1, 2009 at 10:23 AM, Andrew Burgess <span dir="ltr"><<a href="mailto:aab@cichlid.com" target="_blank">aab@cichlid.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> *** glibc detected *** /usr/bin/mythbackend: malloc(): memory<br>
corruption (fast): 0xa895a507 ***<br>
<br>
man malloc reveals:<br>
<br>
Crashes in malloc(), calloc(), realloc(), or free() are almost<br>
always related to heap corruption, such as overflowing an allocated<br>
chunk or freeing the same pointer twice.<br>
Recent versions of Linux libc (later than 5.4.23) and glibc (2.x)<br>
include a malloc() implementation which is tunable via environment<br>
variables. When<br>
MALLOC_CHECK_ is set, a special (less efficient) implementation is<br>
used which is designed to be tolerant against simple errors, such as<br>
double calls<br>
of free() with the same argument, or overruns of a single byte<br>
(off-by-one bugs). Not all such errors can be protected against,<br>
however, and memory<br>
leaks can result. If MALLOC_CHECK_ is set to 0, any detected heap<br>
corruption is silently ignored; if set to 1, a diagnostic message is<br>
printed on<br>
stderr; if set to 2, abort(3) is called immediately; if set to 3, a<br>
diagnostic message is printed on stderr and the program is aborted.<br>
Using a<br>
nonzero MALLOC_CHECK_ value can be useful because otherwise a crash<br>
may happen much later, and the true cause for the problem is then very<br>
hard to<br>
track down.<br>
<br>
---------------------------------<br>
<br>
so try starting mythbackend like this:<br>
<br>
MALLOC_CHECK_=3 /usr/local/bin/mythbackend <other args><br>
<br>
probably by editing the script in /etc/rc.d/init.d (or wherever yours<br>
is)<br>
so you keep the other arguments<br>
<br>
HTH<br>
<br>
<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</blockquote></div><br>