From: Alan Modra <amodra@gmail.com>
To: Sim Tov <smntov@gmail.com>
Cc: Jan Beulich <jbeulich@suse.com>, binutils@sourceware.org
Subject: Re: Cross-compilation related bug
Date: Fri, 22 Jul 2022 12:35:07 +0930 [thread overview]
Message-ID: <YtoT43PEOJ351NLJ@squeak.grove.modra.org> (raw)
In-Reply-To: <CA+X_a+yk-pjTH=SKnZPAn2usCaS9PNquBnApAvbCQO-Yki13YQ@mail.gmail.com>
On Thu, Jul 21, 2022 at 09:40:35PM +0300, Sim Tov via Binutils wrote:
> If you don't have a Windows machine to install MSYS2:
>
> https://www.msys2.org/
>
> We would be more than happy to follow your instructions in a live
> session (e.g. via IRC, etc) and provide you
> with the outputs, logs, screenshots and screen sharing...
I'm sorry, the reality is that trying to debug remotely is extremely
time consuming and frustrating for everyone involved.
> > But maybe one, who is familiar with the internals of binutils, can
> > guess what is wrong, being provided with the file names and lines:
> >
> > binutils-gdb/bfd/cofflink.c:2279
> > binutils-gdb/bfd/coff-x86_64.c:696
All that says to me is "something went wrong", likely long before
the assertions triggered.
If you expect someone to look at your bug, you need to package up a
set of object files so that someone can reproduce the problem by
running the linker on an entirely different machine. Note that the
inputs to the linker are needed, not source files. We don't want to
and can't debug your compiler for you.. That means *all* the inputs
to ld, so system libraries too. Please do test that what you package
up is a complete testcase, by running a cross-linker on a non-windows
machine.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2022-07-22 3:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 13:49 Sim Tov
2022-07-21 14:08 ` Jan Beulich
2022-07-21 14:33 ` Sim Tov
2022-07-21 18:40 ` Sim Tov
2022-07-22 3:05 ` Alan Modra [this message]
2022-07-22 12:29 ` Sim Tov
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=YtoT43PEOJ351NLJ@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=smntov@gmail.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).