Brian Rossa br@f0cal.com
Mon Apr 29 14:00:00 GMT 2019

• Previous message (by thread): [PATCH, BINUTILS, AArch64] Enable Transactional Memory Extension
• Next message (by thread): LD_DEBUG=bindings shows resolution *via* the exe?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Most symbols resolve normally, with the exe "looking" and the libraries
providing. But a small few *appear* to be resolved via the exe itself. For
example,

```
binding file /lib/aarch64-linux-gnu/libc.so.6 [0] to python [0]: normal
symbol `stderr' [GLIBC_2.17]
```

and

```
binding file /lib/aarch64-linux-gnu/libz.so.1 [0] to python [0]: normal
symbol `__stack_chk_guard' [GLIBC_2.17]
```

I only find this for a handful of symbols, such as: __environ, __progname,
__progname_full, __stack_chk_guard, optind, stderr, stdin, stdout

What does this mean?

Cheers!
~br

---

• Previous message (by thread): [PATCH, BINUTILS, AArch64] Enable Transactional Memory Extension
• Next message (by thread): LD_DEBUG=bindings shows resolution *via* the exe?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Binutils mailing list