public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: "Clément Chigot" <chigot@adacore.com>
Cc: "Clément Chigot via Binutils" <binutils@sourceware.org>
Subject: Re: Failure with PR16566 new test on Mingw hosts
Date: Tue, 23 May 2023 12:06:22 +0100	[thread overview]
Message-ID: <e11833fb-31c4-76cf-eebf-27ba4cf8fd2b@redhat.com> (raw)
In-Reply-To: <CAJ307Ei_okkz8cvMRe82T9dVoPNf=KMdTiUCE5rNbEfqR8LoEA@mail.gmail.com>

Hi Clément,

> I've a weird failure on the new test introduced by 496917ce46 and its -print-map-locals. On mingw, when cross-linking to any ELF targets,

So this happens when the *host* is a mingw system, rather than, say,
a Linux system.  That is strange.  Why would the host matter ?

> adding the option results in a crash when writing the output executable:

> It seems that a call to fwrite is failing with EPIPE, when writing the strtab.

> I don't know why but this seems to be triggered by the new call to bfd_canonicalize_symtab introduced when we are logging the local symbols [1]. Any idea about what's
> going on ?

No. :-(  It is definitely weird.

Do you know if the problem is target specific, ie only happening
for certain ELF targets ?

Maybe this is a memory problem.  Possibly the code is using freed
memory, or something like that.  And on Linux hosts the freed memory
is untouched but on mingw hosts the memory is recycled and used for
something else ?  If you run the command under a program like valgrind
to you get any more information ?  Or maybe compiling with address
sanitization enabled ?

Cheers
   Nick



  reply	other threads:[~2023-05-23 11:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23  8:48 Clément Chigot
2023-05-23 11:06 ` Nick Clifton [this message]
2023-05-23 11:37   ` Clément Chigot
2023-05-23 13:11 ` Alan Modra
2023-05-23 15:31   ` Clément Chigot
2023-05-24  0:07     ` Alan Modra
2023-05-24  1:12       ` Alan Modra
2023-05-24  8:56       ` Clément Chigot
2023-05-24  9:33         ` Alan Modra
2023-05-24 11:46           ` Clément Chigot

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=e11833fb-31c4-76cf-eebf-27ba4cf8fd2b@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=chigot@adacore.com \
    /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).