Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 166054 - something is borked in gentoo userland (*** glibc detected *** *: double free or corruption)
Summary: something is borked in gentoo userland (*** glibc detected *** *: double free...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High critical (vote)
Assignee: Gentoo Toolchain Maintainers
Depends on:
Reported: 2007-02-09 11:31 UTC by Markus Rothe (RETIRED)
Modified: 2007-02-10 09:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

ppc64_emerge_info.txt (ppc64_emerge_info.txt,4.13 KB, text/plain)
2007-02-09 11:32 UTC, Markus Rothe (RETIRED)
vlc_double_free_ppc64.txt (vlc_double_free_ppc64.txt,56.94 KB, text/plain)
2007-02-09 11:32 UTC, Markus Rothe (RETIRED)
amd64_emerge_info.txt (amd64_emerge_info.txt,4.10 KB, text/plain)
2007-02-09 11:32 UTC, Markus Rothe (RETIRED)
dspam_double_free_amd64.txt (dspam_double_free_amd64.txt,11.68 KB, text/plain)
2007-02-09 11:34 UTC, Markus Rothe (RETIRED)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Rothe (RETIRED) gentoo-dev 2007-02-09 11:31:57 UTC
I have a serious problem on tree of my systems. glibc detects "double free or corruption":

*** glibc detected *** *: double free or corruption

This does only happen with a few applications and not in every situation. Unfortunately I can reproduce this on ppc64, amd64 and x86 (this is a amd64 machine running x86). I'll attach outputs and 'emerge --info' of the ppc64 and amd64 machine.

I'm currently downgrading to gcc-4.1.1-r1 as I've updated to that version in the timeframe the corruption appeared.
Comment 1 Markus Rothe (RETIRED) gentoo-dev 2007-02-09 11:32:21 UTC
Created attachment 109617 [details]
Comment 2 Markus Rothe (RETIRED) gentoo-dev 2007-02-09 11:32:41 UTC
Created attachment 109618 [details]
Comment 3 Markus Rothe (RETIRED) gentoo-dev 2007-02-09 11:32:54 UTC
Created attachment 109620 [details]
Comment 4 Markus Rothe (RETIRED) gentoo-dev 2007-02-09 11:34:51 UTC
Created attachment 109622 [details]

now this a really mysterious situation: if I change "--user tsr" to "--user markus" the programm does not crash. Unfortunately I've deleted the file triggering this, so I can no longer reproduce... :-/
Comment 5 Markus Rothe (RETIRED) gentoo-dev 2007-02-09 11:37:57 UTC
please note that I've updated glibc on the amd64 system to check if a newer one would fix the problem. So you see glibc-2.5 in "emerge --info", but in the output.
Comment 6 Markus Rothe (RETIRED) gentoo-dev 2007-02-10 07:54:04 UTC
this seems not to be releated to gcc-4.1.1-r3 as downgrading to gcc-4.1.1-r1 did not fix the problem.
Comment 7 Kevin F. Quinn (RETIRED) gentoo-dev 2007-02-10 09:33:48 UTC
"double free or corruption (out)" means that free() detected that it was about to free a chunk from a contiguous set of chunks, but the chunk was outside the range of the set.

What this usually means is that the application is free()'ing memory that it has already free()'ed, or that it is free()'ing a block that wasn't malloc()'ed earlier.  It _could_ mean there's a bug in glibc - but that's less likely.

IOW the first assumption has to be that these are application bugs (rather than glibc).  Report them upstream; if they can reproduce the bug then they're in a much better position to figure it out and fix it :)  In the first instance I suggest reporting the x86 variants.
Comment 8 Markus Rothe (RETIRED) gentoo-dev 2007-02-10 09:50:17 UTC
yes, sound like a plan :-)

after some testing here and there I can not figure out if the above two examples are connected in any way...

I'll close this as INVALID and report this upstream when I have some real data.
Comment 9 Markus Rothe (RETIRED) gentoo-dev 2007-02-10 09:50:27 UTC