public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: binutils@sourceware.org
Subject: Re: [Bug] DWARF-5 section names in PE/PEP and weak symbols
Date: Tue, 15 Feb 2022 20:08:10 +0100	[thread overview]
Message-ID: <877d9whrs5.fsf@Rainer.invalid> (raw)
In-Reply-To: <87bkz8hv09.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 15 Feb 2022 18:58:30 +0100")

Achim Gratz writes:
> So, snprintf seems to behave as expected (it resolves NULL) and the two
> other symbols are resolved even though they should not.  If they had
> resolved to the actual address things might even work, but the actual
> values explain nicely why a program calling through the pointer crashes
> in various horrible ways (depending on what actually is mapped there).

So I've removed the "weak" attribute from snprintf so that it links:

--8<---------------cut here---------------start------------->8---
...packages/binutils-gdb/build (2139)# 
...packages/binutils-gdb/build (2139)# objdump -x /usr/lib/libcygwin.a |less
...packages/binutils-gdb/build (2140)# gcc -Wl,--trace-symbol={fputs,snprintf,thrd_exit} -c -o weak_test.o weak_test.c
...packages/binutils-gdb/build (2141)# gcc -Wl,--trace-symbol={fputs,{a,v,}snprintf,thrd_exit} -o weak_test weak_test.o
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: weak_test.o: reference to snprintf
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: weak_test.o: reference to thrd_exit
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: weak_test.o: reference to fputs
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../lib/libcygwin.a(t-d000578.o): definition of fputs
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../lib/libcygwin.a(t-d001396.o): definition of snprintf
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../lib/libcygwin.a(t-d001527.o): definition of thrd_exit
...packages/binutils-gdb/build (2142)# ./weak_test ; echo $?
snprintf  => 0x0001004012e0     is not equal NULL
fputs     => 0x0001004012c0     is not equal NULL
thrd_exit => 0x0001004012f0     is not equal NULL
sprintf called through symbol
0
...packages/binutils-gdb/build (2143)# nm weak_test.o /bin/cygwin1.dll | egrep ' (fputs|[av]?snprintf|thrd_exit)$'
                 U fputs
                 U snprintf
                 U thrd_exit
00000001801abb10 T asnprintf
00000001801b1610 T fputs
00000001801c0380 T snprintf
00000001801849a0 T thrd_exit
00000001801eec30 T vsnprintf
--8<---------------cut here---------------end--------------->8---


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

  reply	other threads:[~2022-02-15 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 18:27 Achim Gratz
2021-12-15 13:12 ` Nick Clifton
2021-12-20 19:45   ` Achim Gratz
2022-01-23  8:10     ` Achim Gratz
2022-01-29  7:57   ` Achim Gratz
2022-02-13 20:17   ` Achim Gratz
2022-02-14 11:02     ` ASSI
2022-02-15 17:58       ` Achim Gratz
2022-02-15 19:08         ` Achim Gratz [this message]
2022-02-15 20:19         ` Achim Gratz

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=877d9whrs5.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=binutils@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).