From: Ian Lance Taylor <ian@cygnus.com>
To: hjl@varesearch.com
Cc: bfd@cygnus.com
Subject: Re: DWARF read
Date: Fri, 05 Feb 1999 11:57:00 -0000 [thread overview]
Message-ID: <199902051957.OAA25164@subrogation.cygnus.com> (raw)
In-Reply-To: <m108r9q-000AUYC@shanghai.varesearch.com>
From: hjl@varesearch.com (H.J. Lu)
Date: Fri, 5 Feb 1999 11:43:18 -0800 (PST)
I noticed that there is no DWARF read in BFD. As the result, one ld
test failed on Solaris/x86:
gcc -g -I/net/shanghai/local/work/gnu/src/binutils/ld/testsuite/ld-undefined -c -O2 -g /net/shanghai/local/work/gnu/src/binutils/ld/testsuite/ld-undefined/undefined.c
-o tmpdir/undefined.o
/export/home/hjl/build/gnu/bin/binutils/ld/ld-new -e start -o tmpdir/undefined
tmpdir/undefined.o
ld-new: warning: cannot find entry symbol start; defaulting to 08048074
tmpdir/undefined.o: In function `function':
tmpdir/undefined.o(.text+0x4): undefined reference to `this_function_is_not_defined'
PASS: undefined
PASS: undefined function
FAIL: undefined line
However, gdb knows how to read DWARF. Shouldn't it be moved to BFD so
that other problems can access DWARF also?
What vintage sources are you using? Gavin Romig-Koch added DWARF 2
debug reading to BFD in December 1997, and he added DWARF 1 in October
1998. Solaris/x86 almost certainly uses DWARF 1. If you are getting
the above error from recent sources, then there is a bug somewhere.
The gdb debug format parsing code is not in BFD for any format. The
handling of debugging information is central to gdb, and it's never
seemed useful to provide the complex gdb handling to any other
program. BFD has much simpler and less efficient versions of
debugging information handling.
Ian
prev parent reply other threads:[~1999-02-05 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-05 11:43 H.J. Lu
1999-02-05 11:57 ` Ian Lance Taylor [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=199902051957.OAA25164@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=bfd@cygnus.com \
--cc=hjl@varesearch.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).