From: Stefan Liebler <stli@linux.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v5 1/1] memalign: Support scanning for aligned chunks.
Date: Wed, 5 Apr 2023 16:07:24 +0200 [thread overview]
Message-ID: <204afb81-9dc6-f7fe-c707-a4f438815f55@linux.ibm.com> (raw)
In-Reply-To: <xnlejfxpkt.fsf@greed.delorie.com>
On 29.03.23 22:36, DJ Delorie via Libc-alpha wrote:
>
> Thanks! Pushed.
>
On s390 (31bit), I see the test fail:
FAIL: malloc/tst-memalign-2-mcheck
After adding those printfs ...:
diff --git a/malloc/tst-memalign-2.c b/malloc/tst-memalign-2.c
index 4996578e9f..adfebf8384 100644
--- a/malloc/tst-memalign-2.c
+++ b/malloc/tst-memalign-2.c
@@ -72,10 +72,12 @@ do_test (void)
{
tcache_allocs[i].ptr1 = memalign (tcache_allocs[i].alignment,
tcache_allocs[i].size);
CHECK (tcache_allocs[i].ptr1, tcache_allocs[i].alignment);
+ printf ("%d# ptr1=%p\n", i, tcache_allocs[i].ptr1);
free (tcache_allocs[i].ptr1);
/* This should return the same chunk as was just free'd. */
tcache_allocs[i].ptr2 = memalign (tcache_allocs[i].alignment,
tcache_allocs[i].size);
CHECK (tcache_allocs[i].ptr2, tcache_allocs[i].alignment);
+ printf ("%d# ptr2=%p\n", i, tcache_allocs[i].ptr2);
free (tcache_allocs[i].ptr2);
TEST_VERIFY (tcache_allocs[i].ptr1 == tcache_allocs[i].ptr2);
... I've got this output:
0# ptr1=0x55bc71b8
0# ptr2=0x55bc71b8
1# ptr1=0x55bc7210
1# ptr2=0x55bc7260
error: tst-memalign-2.c:83: not true: tcache_allocs[i].ptr1 ==
tcache_allocs[i].ptr2
2# ptr1=0x55bc72e0
2# ptr2=0x55bc72e0
error: 1 test failures
malloc/tst-memalign-2 (without mcheck) is passing.
PASS: malloc/tst-memalign-2
original exit status 0
0# ptr1=0x55c0e190
0# ptr2=0x55c0e190
1# ptr1=0x55c0e190
1# ptr2=0x55c0e190
2# ptr1=0x55c0e1c0
2# ptr2=0x55c0e1c0
Can you please help.
Thanks,
Stefan
next prev parent reply other threads:[~2023-04-05 14:07 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 ` [PATCH v5 1/1] " Adhemerval Zanella Netto
2023-04-12 17:40 ` 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 [this message]
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=204afb81-9dc6-f7fe-c707-a4f438815f55@linux.ibm.com \
--to=stli@linux.ibm.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).