From: fire-eyes <sgtphou@fire-eyes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***
Date: Sat, 19 Nov 2005 08:02:55 -0500 [thread overview]
Message-ID: <437F227F.2010008@fire-eyes.org> (raw)
In-Reply-To: <20051119121057.GA10100@valinor.dynalias.net>
David Morgan wrote:
> It's not kernel related, it's glibc telling you that you screwed up with
> memory allocation somewhere.
>
> The only 'fix' is to fix your code, so no one can help without seeing it
> (apart from maybe listing some common mistakes that cause this).
Okay. My difference is that I see this with apps that I didn't write,
which others don't have issues with. But I haven't seen it in a while,
seems to come and go. Doesn't make much sense, and I have checked my
hardware repeatedly.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-19 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 18:37 [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 *** Michael Sullivan
2005-11-18 20:00 ` fire-eyes
2005-11-18 20:19 ` Michael Sullivan
2005-11-19 11:44 ` fire-eyes
2005-11-19 12:10 ` David Morgan
2005-11-19 13:02 ` fire-eyes [this message]
2005-11-20 14:22 ` Ciaran McCreesh
2005-11-19 14:16 ` [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 *** [SOLVED] Michael Sullivan
2005-11-20 14:23 ` Ciaran McCreesh
2005-11-18 20:50 ` [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 *** John Myers
2005-11-19 2:42 ` Ciaran McCreesh
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=437F227F.2010008@fire-eyes.org \
--to=sgtphou@fire-eyes.org \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox