From: Cyrille Artho <cartho@mordor.ch>
To: binutils@sourceware.cygnus.com
Subject: More information about: Bug in ar?
Date: Wed, 19 Jul 2000 02:43:00 -0000 [thread overview]
Message-ID: <3975785A.D2B558F8@mordor.ch> (raw)
A few things I did not mention before: I always built the files from
scratch, because running 'ar ru...' produced too many errors.
The object files from g++ are usually the same, although the *sometimes*
differ. The difference is not, as I previously suspected, in the
mangling strings coming from g++ (these never differ). The outputs of
'nm' are always equal, except for (sometimes) missing symbols and, of
course, offsets.
I finally could reproduce an output where the .o files differed (which
is not often the case) and where 'nm' said "xy.o truncated". Therefore,
the problem may lie in g++.
I will now investigate whether the source code that produces the error
always includes some C code in a C++ file that has not yet been declared
extern "C".
Possibly, the error "file xy truncated" results from g++, while the
error messages
BFD: UTraceOut.o: invalid string offset 1769472 >= 958 for section
`.shstrtab'
hint at some problem in BFD.
--
Regards,
Cyrille Artho - http://artho.com
Alcohol is the anesthesia by which we endure the operation of life.
-- George Bernard Shaw
next reply other threads:[~2000-07-19 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 2:43 Cyrille Artho [this message]
2000-07-19 3:26 ` Alan Modra
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=3975785A.D2B558F8@mordor.ch \
--to=cartho@mordor.ch \
--cc=binutils@sourceware.cygnus.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).