From: Usman Akinyemi <usmanakinyemi202@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC]: Test Were failing on Fedora Linux.
Date: Sat, 9 Nov 2024 09:59:09 -0500 [thread overview]
Message-ID: <CAPSxiM9AwwmoPcoGs57A8HtwZVMOH5Kzgsa4ju7DqhFjMAeKSQ@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD2=imvtamewLN+VvKDK83aL7NhGAb=MjvHQ2OwaK-n5UQ@mail.gmail.com>
On Sat, Nov 9, 2024 at 9:01 AM Christian Couder
<christian.couder@gmail.com> wrote:
>
> Hi Usman,
>
> On Sat, Nov 9, 2024 at 10:33 AM Usman Akinyemi
> <usmanakinyemi202@gmail.com> wrote:
> >
> > On Sat, Nov 9, 2024 at 3:12 AM Christian Couder
> > <christian.couder@gmail.com> wrote:
>
> > > You can run each failing test with some options like -i and -v to get
> > > more information, like for example:
> > >
> > > $ ./t0000-basic.sh -i -v
> >
> > I was using make before. I tried to run the single test as above, the error was
> > ERROR: ld.so: object 'libc_malloc_debug.so.0' from LD_PRELOAD cannot
> > be preloaded (cannot open shared object file): ignored
> > I tried to check this online, but, all the solutions I found were not
> > resolving it.
>
> First, as a workaround, maybe you can try:
>
> $ TEST_NO_MALLOC_CHECK=1 ./t0000-basic.sh -i -v
>
> to see if things work when disabling malloc checks.
>
> Anyway the issue might be related to how your shared libraries are
> installed, so using ldconfig might help:
>
> $ sudo ldconfig
>
> Alternatively you can try replacing the following line in t/test-lib.sh:
>
> LD_PRELOAD="libc_malloc_debug.so.0"
>
> with:
>
> LD_PRELOAD="/usr/lib/libc_malloc_debug.so.0"
>
> This is a hack but it might help understand what's going on if it works.
Hi Christian.
Thanks for this, the problem was due to the architecture, the one
/usr/lib/libc_malloc_debug.so.0 was 32bit,
I had to download the 64bit by downloading glibc-utils.x86_64. I did
not face this when I was using Arch Linux.
Thank you.
Usman.
>
> > I look for libc_malloc_debug.so.0 and it is located in /usr/lib
> > uniqueusman@fedora:~/git/t$ sudo find / -name "libc_malloc_debug.so.0"
> > find: ‘/run/user/1000/gvfs’: Permission denied
> > find: ‘/run/user/1000/doc’: Permission denied
> > /usr/lib/libc_malloc_debug.so.0
>
> Yeah, not sure why it doesn't work while you have it.
>
> Best,
> Christian.
prev parent reply other threads:[~2024-11-09 14:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 6:01 [RFC]: Test Were failing on Fedora Linux Usman Akinyemi
2024-11-09 8:12 ` Christian Couder
2024-11-09 9:32 ` Usman Akinyemi
2024-11-09 14:01 ` Christian Couder
2024-11-09 14:35 ` Andreas Schwab
2024-11-09 15:02 ` Usman Akinyemi
2024-11-09 16:05 ` Todd Zullinger
2024-11-09 19:00 ` Jeff King
2024-11-09 19:12 ` Usman Akinyemi
2024-11-11 3:11 ` Junio C Hamano
2024-11-11 7:01 ` [PATCH] test-lib: check malloc debug LD_PRELOAD before using Jeff King
2024-11-13 10:19 ` Toon Claes
2024-11-14 1:27 ` Jeff King
2024-11-14 1:39 ` [PATCH 2/1] test-lib: move malloc-debug setup after $PATH setup Jeff King
2024-11-20 13:51 ` Toon Claes
2024-11-20 23:26 ` Junio C Hamano
2024-11-09 19:09 ` [RFC]: Test Were failing on Fedora Linux Usman Akinyemi
2024-11-09 14:59 ` Usman Akinyemi [this message]
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=CAPSxiM9AwwmoPcoGs57A8HtwZVMOH5Kzgsa4ju7DqhFjMAeKSQ@mail.gmail.com \
--to=usmanakinyemi202@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).