This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug malloc/19243] reused_arena can pick an arena on the free list, leading to an assertion failure and reference count corruption
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 29 Feb 2016 19:52:21 +0000
- Subject: [Bug malloc/19243] reused_arena can pick an arena on the free list, leading to an assertion failure and reference count corruption
- Auto-submitted: auto-generated
- References: <bug-19243-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19243
--- Comment #8 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Nick Alcock from comment #7)
> I still see aborts of tst-malloc-thread-exit in 2.23 after this fix, with
> less-than-useful stacks (on x86-64, compiled with a GCC 4.9.4 prerelease).
> This may be this bug or, I suppose, may be something else:
>
> (gdb) bt
> #0 0x00007ffff7a6d1b7 in raise () from
> /usr/src/glibc/x86_64-mutilate/libc.so.6
> #1 0x00007ffff7a6e60a in __GI_abort () at abort.c:89
Is there a message printed before that? What's the actual failure?
If there is no message, you might get a better backtrace if you compile the
test case with -O1 (or -fno-optimize-sibling-calls, I think).
The abort isn't in malloc itself, I think, so it's better to file a new bug for
this.
--
You are receiving this mail because:
You are on the CC list for the bug.