public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: binutils@sourceware.org
Subject: Re: [Bug] DWARF-5 section names in PE/PEP and weak symbols
Date: Mon, 14 Feb 2022 12:02:59 +0100	[thread overview]
Message-ID: <87y22d7lss.fsf@Otto.invalid> (raw)
In-Reply-To: <87mtiumsgt.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 13 Feb 2022 21:17:38 +0100")

Achim Gratz writes:
> In fact it appears that with 2.38 weak symbols are in fact working
> correctly for the handful examples that I've come up with.  I'll have to
> go back to the original example that produced buggy behaviour (grep-3.7
> w/o patched gnulib threadlib.m4) and see if that's now working as well
> (it may not, since the libraries have all been produced by earlier ld,
> but it seems worth trying).

So, grep-3.7 does still not work when compiled with weak symbols
enabled.  It seems that it does not properly resoves the symbol using the
DLL at runtime and/or misses to take the actual base address of the DLL
into account (which differs from the one that it had when it was built
due to rebasing).


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

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2022-02-14 11:03 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 [this message]
2022-02-15 17:58       ` Achim Gratz
2022-02-15 19:08         ` Achim Gratz
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=87y22d7lss.fsf@Otto.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).