public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stsp at users dot sourceforge.net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30256] ldd says "statically linked" when its not
Date: Tue, 21 Mar 2023 09:45:16 +0000	[thread overview]
Message-ID: <bug-30256-131-df3oj6blRl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30256-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30256

--- Comment #2 from Stas Sergeev <stsp at users dot sourceforge.net> ---
libmain.so:     file format elf64-x86-64

Program Header:
    LOAD off    0x0000000000000000 vaddr 0x0000000000000000 paddr
0x0000000000000000 align 2**12
         filesz 0x00000000000004b0 memsz 0x00000000000004b0 flags r--
    LOAD off    0x0000000000001000 vaddr 0x0000000000001000 paddr
0x0000000000001000 align 2**12
         filesz 0x0000000000000111 memsz 0x0000000000000111 flags r-x
    LOAD off    0x0000000000002000 vaddr 0x0000000000002000 paddr
0x0000000000002000 align 2**12
         filesz 0x00000000000000a4 memsz 0x00000000000000a4 flags r--
    LOAD off    0x0000000000002e68 vaddr 0x0000000000003e68 paddr
0x0000000000003e68 align 2**12
         filesz 0x00000000000001a0 memsz 0x00000000000001a8 flags rw-
 DYNAMIC off    0x0000000000002e78 vaddr 0x0000000000003e78 paddr
0x0000000000003e78 align 2**3
         filesz 0x0000000000000150 memsz 0x0000000000000150 flags rw-
    NOTE off    0x00000000000002a8 vaddr 0x00000000000002a8 paddr
0x00000000000002a8 align 2**3
         filesz 0x0000000000000020 memsz 0x0000000000000020 flags r--
    NOTE off    0x00000000000002c8 vaddr 0x00000000000002c8 paddr
0x00000000000002c8 align 2**2
         filesz 0x0000000000000024 memsz 0x0000000000000024 flags r--
0x6474e553 off    0x00000000000002a8 vaddr 0x00000000000002a8 paddr
0x00000000000002a8 align 2**3
         filesz 0x0000000000000020 memsz 0x0000000000000020 flags r--
EH_FRAME off    0x0000000000002000 vaddr 0x0000000000002000 paddr
0x0000000000002000 align 2**2
         filesz 0x0000000000000024 memsz 0x0000000000000024 flags r--
   STACK off    0x0000000000000000 vaddr 0x0000000000000000 paddr
0x0000000000000000 align 2**4
         filesz 0x0000000000000000 memsz 0x0000000000000000 flags rw-
   RELRO off    0x0000000000002e68 vaddr 0x0000000000003e68 paddr
0x0000000000003e68 align 2**0
         filesz 0x0000000000000198 memsz 0x0000000000000198 flags r--

Dynamic Section:
  INIT                 0x0000000000001000
  FINI                 0x0000000000001104
  INIT_ARRAY           0x0000000000003e68
  INIT_ARRAYSZ         0x0000000000000008
  FINI_ARRAY           0x0000000000003e70
  FINI_ARRAYSZ         0x0000000000000008
  GNU_HASH             0x00000000000002f0
  STRTAB               0x00000000000003a8
  SYMTAB               0x0000000000000318
  STRSZ                0x0000000000000059
  SYMENT               0x0000000000000018
  PLTGOT               0x0000000000003fe8
  RELA                 0x0000000000000408
  RELASZ               0x00000000000000a8
  RELAENT              0x0000000000000018
  RELACOUNT            0x0000000000000003

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-03-21  9:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21  8:27 [Bug dynamic-link/30256] New: " stsp at users dot sourceforge.net
2023-03-21  9:19 ` [Bug dynamic-link/30256] " schwab@linux-m68k.org
2023-03-21  9:45 ` stsp at users dot sourceforge.net [this message]
2023-03-21 10:07 ` schwab@linux-m68k.org
2023-03-21 11:26 ` stsp at users dot sourceforge.net
2023-03-21 11:56 ` schwab@linux-m68k.org
2023-03-21 12:15 ` stsp at users dot sourceforge.net
2023-03-21 12:59 ` stsp at users dot sourceforge.net
2023-03-21 13:24 ` schwab@linux-m68k.org
2023-03-21 15:09 ` stsp at users dot sourceforge.net

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-30256-131-df3oj6blRl@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).