From: "Mark E." <firstname.lastname@example.org>
Subject: Re: .eh_frame problem
Date: Wed, 03 Mar 1999 21:00:00 -0000 [thread overview]
Message-ID: <199903040500.FAA54290@out4.ibm.net> (raw)
> section contains data rather than code? If there is, then we should
> figure out how to get that information to md_maybe_text, as should already
> work for the BFD_ASSEMBLER version of gas.
The problem does goes away when using BFD_ASSEMBLER gas. But
I'll take a look and see if there is a solution for non-BFD_ASSEMBLER
gas. We'd use BFD_ASSEMBER gas in 2.9.1 but if you'll recall it has
that bug I reported and you fixed in late October where incorrect fixups
are written out making the object files unusable.
next prev parent reply other threads:[~1999-03-03 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-02 21:56 Mark E.
1999-03-03 16:53 ` Ian Lance Taylor
1999-03-03 21:00 ` Mark E. [this message]
1999-03-03 21:15 ` Mark E.
1999-03-04 14:32 ` Ian Lance Taylor
1999-03-03 7:17 Mark E.
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).