From: Andrea Barisani <lcars@gentoo.org>
To: mlmmj@mlmmj.org
Subject: Re: mlmmj-process dies with "free(): invalid next size"
Date: Sun, 12 Nov 2006 15:19:58 +0000 [thread overview]
Message-ID: <20061112151958.GH28840@fuse.inversepath.com> (raw)
In-Reply-To: <3629.130.83.236.83.1163172510.squirrel@130.83.185.210>
On Sun, Nov 12, 2006 at 12:26:08PM +0100, Mads Martin Joergensen wrote:
> * Andrea Barisani <lcars@gentoo.org> [Nov 11. 2006 20:54]:
> > > > ps. The versions I used to test weren't patched.
> > >
> > > Can you please try RC4 with the latest patch from Morten?
> >
> > We get this too: mlmmj-process: *** glibc detected *** free():
> > invalid next size (fast): 0x116383a8 ***
> >
> > RC4 doesn't solve the issue (unless there's some patch against it that I'm
> > missing).
>
> There was this patch from Morten:
>
> http://mlmmj.mmj.dk/~mortenp/patch-mlmmj-1.2.12_RC4-gethdrline.diff
>
> --
> Mads Martin Joergensen, http://mmj.dk
> "Why make things difficult, when it is possible to make them cryptic
> and totally illogical, with just a little bit more effort?"
> -- A. P. J.
Ok I can confirm that with the patch we are still getting the error.
--
Andrea Barisani <lcars@gentoo.org> .*.
Gentoo Linux Infrastructure Developer V
( )
PGP-Key 0x864C9B9E http://dev.gentoo.org/~lcars/pubkey.asc ( )
0A76 074A 02CD E989 CE7F AC3F DA47 578E 864C 9B9E ^^_^^
"Pluralitas non est ponenda sine necessitate"
next prev parent reply other threads:[~2006-11-12 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 15:28 mlmmj-process dies with "free(): invalid next size" Christoph Wilke
2006-11-11 19:18 ` Mads Martin Joergensen
2006-11-11 19:55 ` Andrea Barisani
2006-11-12 11:26 ` Mads Martin Joergensen
2006-11-12 15:14 ` Andrea Barisani
2006-11-12 15:19 ` Andrea Barisani [this message]
2006-11-12 21:32 ` Morten K. Poulsen
2006-11-13 15:00 ` Christoph Wilke
2006-11-13 21:30 ` Christoph Wilke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061112151958.GH28840@fuse.inversepath.com \
--to=lcars@gentoo.org \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.