From: Tavis Ormandy <taviso@gmail.com>
To: binutils@sourceware.org
Subject: Re: BFD misreading symbols from ancient SysV COFF objects
Date: Thu, 26 May 2022 13:37:23 -0000 (UTC) [thread overview]
Message-ID: <t6nvqj$k48$1@ciao.gmane.io> (raw)
In-Reply-To: <t3l4cg$knk$1@ciao.gmane.io>
On 2022-04-19, Tavis Ormandy via Binutils wrote:
> Hello, I've been doing some software archeology for fun and have
> found an interesting COFF object file for SysV386. It seems to have been
> compiled with GCC, the link timestamp is Sat Sep 8 06:23:50 1990, so
> probably GCC 1.3X.
>
> I was hoping I might just be able to `objcopy -O elf32-i386 foo.o fooelf.o`,
> but sadly that didn't work... but it *almost* works and maybe I'm just
> doing something wrong...
I was able to get this working, FYI. It does work okay in binutils-2.38,
I had assumed my distribution's binutils was modern enough, but earlier
versions can crash or give wrong output!
In case anyone would like to read about it, https://lock.cmpxchg8b.com/linux123.html
Tavis.
--
_o) $ lynx lock.cmpxchg8b.com
/\\ _o) _o) $ finger taviso@sdf.org
_\_V _( ) _( ) @taviso
prev parent reply other threads:[~2022-05-26 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 1:48 Tavis Ormandy
2022-05-26 13:37 ` Tavis Ormandy [this message]
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='t6nvqj$k48$1@ciao.gmane.io' \
--to=taviso@gmail.com \
--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).