[gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***

[gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***

[Michael Sullivan]

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?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***

[fire-eyes]

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.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***

[Michael Sullivan]

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?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***

[fire-eyes]

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...
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***

[David Morgan]

On 06:44 Sat 19 Nov     , fire-eyes wrote:
> 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...

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).

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***

[fire-eyes]

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

Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***

[Ciaran McCreesh]

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

On Sat, 19 Nov 2005 08:02:55 -0500 fire-eyes <sgtphou@fire-eyes.org>
wrote:
| 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.

Well... Here's the thing... If you're using an app which triggers that
message, then the app is broken. However, were detection not turned on,
the app would instead behave randomly in such a way that it might carry
on working. So whilst you could turn off the detection, it's probably
not a good idea because you'd end up with random, hard to trace memory
corruption...

-- 
Ciaran McCreesh : Gentoo Developer (Look! Shiny things!)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 *** [SOLVED]

[Michael Sullivan]

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

Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 *** [SOLVED]

[Ciaran McCreesh]

[-- Attachment #1: Type: text/plain, Size: 880 bytes --]

On Sat, 19 Nov 2005 08:16:19 -0600 Michael Sullivan
<michael@espersunited.com> wrote:
| 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...

Consider using boost::shared_ptr<> instead. You don't have to worry
about delete or exception-checking then.

-- 
Ciaran McCreesh : Gentoo Developer (Look! Shiny things!)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***

[John Myers]

[-- Attachment #1: Type: text/plain, Size: 402 bytes --]

On Friday 18 November 2005 10:37, Michael Sullivan wrote:
> 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?
Probably an error in your program. Check for the same kinds of things which 
could cause a segfault, i.e. pointer and array problems

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] *** glibc detected *** malloc(): memory corruption (fast): 0x081fb2c1 ***

[Ciaran McCreesh]

[-- Attachment #1: Type: text/plain, Size: 513 bytes --]

On Fri, 18 Nov 2005 12:37:33 -0600 Michael Sullivan
<michael@espersunited.com> wrote:
| 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?

You screwed up some dynamic memory allocation somewhere.

-- 
Ciaran McCreesh : Gentoo Developer (Look! Shiny things!)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]