public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mkh199740 at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/64234] Statically sanitized executable does not export ASan symbols
Date: Tue, 31 May 2022 08:36:10 +0000	[thread overview]
Message-ID: <bug-64234-4-8o2O9xfwlY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64234-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64234

lo1ol <mkh199740 at mail dot ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mkh199740 at mail dot ru

--- Comment #6 from lo1ol <mkh199740 at mail dot ru> ---
I've the same problem when try to link at runtime shared library compiled with
static asan. Here is minimal example:

echo '
#include <stdlib.h>
#include <stdio.h>

void f(){
    int* x = new int;
    printf("kek\n");
}' > lib.cpp

echo '
#include <dlfcn.h>
#include <stdio.h>
int main() {
    printf("lol\n");
    void* handler = dlopen("./libkek.so", RTLD_NOW);
    if (!handler)
        return 1;

    void (* func)() = reinterpret_cast<void(*)()>(dlsym(handler, "_Z1fv"));
    printf("kek\n");
    func();
    printf("cheburek\n");
}' > main.cpp


g++ -fsanitize=address -static-libasan -static-libstdc++ -static-libgcc -fPIC
-shared lib.cpp -o libkek.so
g++ -fsanitize=address -static-libasan -static-libstdc++ -static-libgcc -ldl
main.cpp
LD_DEBUG=libs ./a.out; echo $?

Part of the output:
...
    347802:     initialize program: ./a.out
    347802:
    347802:
    347802:     transferring control: ./a.out
    347802:
lol
    347802:     ./libkek.so: error: symbol lookup error: undefined symbol:
__asan_unregister_globals (fatal)
    347802:
    347802:     calling fini: ./a.out [0]
    347802:
    347802:
    347802:     calling fini: /lib/x86_64-linux-gnu/libm.so.6 [0]
    347802:


With clang everything is ok....

GCC version 12.1
System: Ubuntu 21.10

  parent reply	other threads:[~2022-05-31  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09  9:35 [Bug sanitizer/64234] New: " y.gribov at samsung dot com
2014-12-09 10:02 ` [Bug sanitizer/64234] " jakub at gcc dot gnu.org
2014-12-09 10:18 ` y.gribov at samsung dot com
2014-12-09 10:22 ` jakub at gcc dot gnu.org
2014-12-09 10:35 ` y.gribov at samsung dot com
2022-05-31  8:36 ` mkh199740 at mail dot ru [this message]
2022-07-18 13:07 ` boris at kolpackov dot net
2022-11-12  2:55 ` mkh199740 at mail dot ru

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-64234-4-8o2O9xfwlY@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).