public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] tests: Add -ldl to dwfl_proc_attach_LDFLAGS
Date: Fri, 19 Nov 2021 11:57:14 +0100	[thread overview]
Message-ID: <YZeDCkIFczMMT6qw@wildebeest.org> (raw)
In-Reply-To: <20211118222026.GB2074@altlinux.org>

Hi Dmitry,

On Fri, Nov 19, 2021 at 01:20:26AM +0300, Dmitry V. Levin wrote:
> On Thu, Nov 18, 2021 at 10:23:41PM +0100, Mark Wielaard wrote:
> > dwfl-proc-attach uses (overrides) dlopen (so it does nothing).  This
> > seems to cause a versioned dlopen symbol to be pulled in when building
> > with LTO. Resulting in a link failure (when dlopen isn't integrated
> > into libc):
> >
> > /usr/bin/ld: dwfl-proc-attach.o (symbol from plugin): undefined
> > reference to symbol 'dlopen@@GLIBC_2.2.5'
> > /usr/bin/ld: /usr/lib64/libdl.so.2: error adding symbols: DSO missing
> > from command line collect2: error: ld returned 1 exit status
> >
> > So simply explicitly add -ldl to the LDFLAGS.
> [...]
> Let's make clear what's going on here.  First of all, dwfl-proc-attach.c
> does not use dlopen so it doesn't pull it in and doesn't need -ldl.
> In regular builds, dwfl-proc-attach.o is linked with ../libdw/libdw.so
> which in turn uses dlopen and is already linked with -ldl.
> When elfutils is configured with --enable-gprof or --enable-gcov,
> BUILD_STATIC is enabled and dwfl-proc-attach.o is linked with
> ../libdw/libdw.a -lz $(zip_LIBS) $(libelf) $(libebl) -ldl -lpthread
> which already contains -ldl.
> In any case, I fail to understand why dwfl-proc-attach might need
> an extra -ldl, especially in LDFLAGS which goes before LDADD
> in the linking command.

Agreed. It isn't totally clear why lto causes dlopen to be "pulled in"
(which is probably the wrong technical term). But it really
does. Instead of adding -ldl to LDFLAGS you can also remove the dlopen
from the testcase:

diff --git a/tests/dwfl-proc-attach.c b/tests/dwfl-proc-attach.c
index d02e9fc0..0c5e8622 100644
--- a/tests/dwfl-proc-attach.c
+++ b/tests/dwfl-proc-attach.c
@@ -114,9 +114,5 @@ main (int argc __attribute__ ((unused)),
    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;
-}
 
 #endif /* __linux__ */

Which also makes the linker happy, but removes the valgrind workaround.

Cheers,

Mark


  reply	other threads:[~2021-11-19 10:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 21:23 Mark Wielaard
2021-11-18 22:20 ` Dmitry V. Levin
2021-11-19 10:57   ` Mark Wielaard [this message]
2021-11-19 16:58   ` Florian Weimer
2021-11-19 22:12     ` Dmitry V. Levin
2021-11-20 14:18       ` Mark Wielaard
2021-11-25 13:35         ` Mark Wielaard
2021-11-25 14:38         ` Dmitry V. Levin

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=YZeDCkIFczMMT6qw@wildebeest.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=ldv@altlinux.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).