From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/27366] 0.183: test suite is failing on linking dwfl-proc-attach
Date: Sun, 07 Feb 2021 22:33:13 +0000 [thread overview]
Message-ID: <bug-27366-10460-pp81PsADKu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27366-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27366
--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
I see you are using -flto=auto. Sadly LTO isn't supported at the moment.
Although it would be nice if it didn't totally break with -flto-partition=none.
The problem with lto might be:
/* HACK. This is a simple workaround for a combination of old glibc
and valgrind. libdw will try to dlopen libdebuginfod this causes
some unsuppressable memory leak warnings when the process is
multi-threaded under valgrind because of some bad backtraces.
So simply override dlopen and always return NULL so libdebuginfod
(and libcurl) are never loaded. This test doesn't rely on
libdebuginfod anyway. */
void *dlopen (void)
{
return NULL;
}
Maybe it needs some __attribute__((__used__)) to make sure it is kept around?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-07 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 22:02 [Bug general/27366] New: " kloczko.tomasz at gmail dot com
2021-02-07 22:03 ` [Bug general/27366] " kloczko.tomasz at gmail dot com
2021-02-07 22:26 ` mark at klomp dot org
2021-02-07 22:33 ` mark at klomp dot org [this message]
2021-02-07 22:33 ` [Bug general/27366] 0.183: test suite is failing on linking dwfl-proc-attach (with lto) mark at klomp dot org
2021-11-11 15:05 ` mark at klomp dot org
2021-11-11 15:22 ` kloczko.tomasz at gmail dot com
2021-11-11 15:28 ` kloczko.tomasz at gmail dot com
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=bug-27366-10460-pp81PsADKu@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).