From: Michael Sullivan <michael@espersunited.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 *** [SOLVED]
Date: Sat, 19 Nov 2005 08:16:19 -0600 [thread overview]
Message-ID: <1132409779.10315.5.camel@camille.espersunited.com> (raw)
In-Reply-To: <437F1020.6000209@fire-eyes.org>
On Sat, 2005-11-19 at 06:44 -0500, fire-eyes wrote:
> Michael Sullivan wrote:
> > On Fri, 2005-11-18 at 15:00 -0500, fire-eyes wrote:
> >
> >>Michael Sullivan wrote:
> >>
> >>>I don't really know who to ask about this error. I searched for an
> >>>explanation on Google and it gave me a link to the Gentoo German forums,
> >>>so I thought maybe someone here could help me with this.
> >>>
> >>>I wrote a Qt program. It compiles just fine, but when I try to run it I
> >>>get this:
> >>>
> >>>michael@camille ~/projects/c++/myFantasy/main/src $ ./src
> >>>*** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1
> >>>***
> >>>Aborted
> >>>
> >>>
> >>>Being fairly inexperienced with C++ I have no idea what this means. Is
> >>>this a problem with my program or with my system. Is there a way to fix
> >>>it? Can anyone at least explain to me what it means?
> >>
> >>Are you running a grsecurity and or pax kernel?
> >>
> >>I get this kind of crap left and right with it... Sometimes. Very
> >>unpredictable. Very annoying.
> >>
> >
> >
> > I don't know what "grsecurity" or "pax kernel" are. I use genkernel.
> > Here's the output of my uname:
> >
> > michael@camille ~ $ uname -a
> > Linux camille 2.6.14-gentoo-r2 #1 Thu Nov 17 07:30:09 CST 2005 i686
> > Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux
> >
> >
> > Out of curiosity, how do you get around this error?
> >
>
> Well, you aren't running one then :) As for getting around, I haven't
> figured out a way. It's very frustrating to note that I haven't been
> able to ever find help about this. Makes one feel on your own...
Actually, I solved the error for my situation last night - I just forgot
to write it in as SOLVED. I had created a temporary pointer, then
assigned the temporary pointer to a variable I was planning to return
from a method, then deleted the temporary pointer. I'm not used to
using pointers. I've always heard that you should always delete your
pointers when you're done with them and for some reason I thought the
delete keyword deleted the pointer instead of the memory it was pointing
at...
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-19 14:25 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
2005-11-20 14:22 ` Ciaran McCreesh
2005-11-19 14:16 ` Michael Sullivan [this message]
2005-11-20 14:23 ` [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 *** [SOLVED] 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=1132409779.10315.5.camel@camille.espersunited.com \
--to=michael@espersunited.com \
--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