From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: "Xi Ruoyao" <xry111@xry111.site>,
"Cristian Rodríguez" <crrodriguez@opensuse.org>
Cc: DJ Delorie <dj@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v5 1/1] memalign: Support scanning for aligned chunks.
Date: Wed, 12 Apr 2023 14:33:07 -0300 [thread overview]
Message-ID: <e9283931-a7da-4c49-6c79-e0f1be84c565@linaro.org> (raw)
In-Reply-To: <e222a231f5684cfa2680e500d5579c7d878a6208.camel@xry111.site>
On 12/04/23 14:04, Xi Ruoyao wrote:
> On Thu, 2023-03-30 at 18:43 -0300, Cristian Rodríguez via Libc-alpha
> wrote:
>> On Thu, Mar 30, 2023 at 7:50 AM Adhemerval Zanella Netto <
>> adhemerval.zanella@linaro.org> wrote:
>>
>>> Do you have any testcase that triggers it?
>>
>> I'll try.. cannot compile ripgrep with debug info either ..because this
>> commit also makes rustc crash with the same message.😕
>
> On LoongArch (with a GCC 12.2 but LoongArch backend patched to match GCC
> trunk), this causes an almost deterministic failure of malloc/tst-
> malloc-thread-fail-malloc-hugetlb2:
>
> FAIL: malloc/tst-malloc-thread-fail-malloc-hugetlb2
> original exit status 1
> error: exit status 139 from child process
>
I can reproduce on x86_64 as well in a non-deterministic manner (with multiple
'rm malloc/*.out && make malloc/tests -j24'. The core file shows internal
metadata corruption:
$ gdb elf/ld.so core
[...]
#0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0)
at pthread_kill.c:44
44 return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0;
(gdb) bt
#0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0)
at pthread_kill.c:44
#1 0x00007fae15090017 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
#2 0x00007fae1503e326 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3 0x00007fae150264b1 in __GI_abort () at abort.c:79
#4 0x00007fae150272cc in __libc_message (fmt=fmt@entry=0x7fae151b0632 "%s\n") at ../sysdeps/posix/libc_fatal.c:150
#5 0x00007fae1509b873 in malloc_printerr (str=str@entry=0x7fae151b3458 "free(): double free detected in tcache 2")
at malloc.c:5847
#6 0x00007fae1509dd5b in _int_free (av=0x7fae1524cac0 <main_arena>, p=0x7fae14e00290, have_lock=0) at malloc.c:4508
#7 0x00007fae150a07bb in __GI___libc_free (mem=<optimized out>) at malloc.c:3386
#8 0x00007fae15445594 in ?? ()
#9 0x00007fae14e002a0 in ?? ()
#10 0x73afe8780d804600 in ?? ()
#11 0x00007ffec090cc68 in ?? ()
#12 0x00007fae1544622b in ?? ()
#13 0x0000000000000000 in ?? ()
next prev parent reply other threads:[~2023-04-12 17:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 3:58 [PATCH v1 " DJ Delorie
2022-07-19 2:54 ` Carlos O'Donell
2022-07-19 3:57 ` [PATCH v2 " DJ Delorie
2022-07-19 9:19 ` Florian Weimer
2022-07-19 17:32 ` DJ Delorie
2022-07-20 0:32 ` [PATCH v3 " DJ Delorie
2022-07-22 20:21 ` DJ Delorie
2022-07-22 20:28 ` Joseph Myers
2022-07-28 19:50 ` [PATCH v4 " DJ Delorie
2022-08-17 19:00 ` DJ Delorie
2022-11-10 21:40 ` Ping^2: " DJ Delorie
2023-03-20 21:49 ` Ping^3: " DJ Delorie
2023-03-28 19:07 ` Adhemerval Zanella Netto
2023-03-29 4:20 ` [PATCH v5 " DJ Delorie
2023-03-29 19:41 ` Adhemerval Zanella Netto
2023-03-29 20:36 ` DJ Delorie
2023-03-30 10:04 ` Cristian Rodríguez
2023-03-30 10:50 ` Adhemerval Zanella Netto
2023-03-30 21:43 ` Cristian Rodríguez
2023-04-12 17:04 ` Xi Ruoyao
2023-04-12 17:16 ` DJ Delorie
2023-04-12 17:26 ` Xi Ruoyao
2023-04-13 1:52 ` [PATCH v6 " DJ Delorie
2023-04-13 5:51 ` Xi Ruoyao
2023-04-17 21:48 ` Carlos O'Donell
2023-04-18 1:25 ` [PATCH v7] " DJ Delorie
2023-04-18 13:58 ` Carlos O'Donell
2023-04-18 15:02 ` DJ Delorie
2023-04-12 17:33 ` Adhemerval Zanella Netto [this message]
2023-04-12 17:40 ` [PATCH v5 1/1] " DJ Delorie
2023-04-12 18:01 ` Adhemerval Zanella Netto
2023-04-13 1:57 ` DJ Delorie
2023-04-13 10:46 ` Adhemerval Zanella Netto
2023-04-05 14:07 ` Stefan Liebler
2023-04-05 17:58 ` DJ Delorie
2023-04-11 11:40 ` Stefan Liebler
2023-04-12 11:23 ` Stefan Liebler
2023-03-31 15:39 ` Adhemerval Zanella Netto
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=e9283931-a7da-4c49-6c79-e0f1be84c565@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=crrodriguez@opensuse.org \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=xry111@xry111.site \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).