From: alexandre schenberg <ale.schenberg@yandex.com>
To: Andrew Bell <andrew.bell.ia@gmail.com>
Cc: libc-help@sourceware.org
Subject: Re:SIGSEGV when running 32bit apps
Date: Sat, 06 May 2023 20:54:04 -0300 [thread overview]
Message-ID: <1509221683417244@r3jg5wtwbxytj3pm.iva.yp-c.yandex.net> (raw)
In-Reply-To: <CACJ51z1sAMWCytMm2FVzfpCDZM5KKRzbDa=uSePgXMpVV4=bXw@mail.gmail.com>
It's quite simple. Most times I try to run a 32bit application that I built from source, I end with a segmentation fault with the exceptions that I listed in my first post.
I built the majority of them with -Wl,--dynamic-link=/usr/lib32/ld-2.17.so, which is a symbolic link to /media/34GB/Arquivos-de-Programas-Linux-32bit/Glibc-2.17/lib/ld-2.17.so where it dwells. So the versions match and the loader can be find.
I believe the source of the segmentation faults is using some auxiliary 64bit glibc libraries, but precisely what and how to solve it remains a mystery to me
next prev parent reply other threads:[~2023-05-06 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 0:16 SIGSEGV " alexandre schenberg
2023-05-05 1:33 ` Andrew Bell
2023-05-06 23:54 ` alexandre schenberg [this message]
2023-05-07 0:55 ` 김찬
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=1509221683417244@r3jg5wtwbxytj3pm.iva.yp-c.yandex.net \
--to=ale.schenberg@yandex.com \
--cc=andrew.bell.ia@gmail.com \
--cc=libc-help@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).