From: Lars Malmborg <lars.malmborg@precisebiometrics.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Trace32 running eCos
Date: Wed, 09 Jun 1999 01:05:00 -0000 [thread overview]
Message-ID: <375E2011.F29E60C2@precisebiometrics.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
Hi!
I'm trying to make eCos run in the demo version of the Trace32 debugger,
as found on Lauterbach's home page
( http://www.lauterbach.de/simarm.exe )...
When I load a generated ELF it says:
loading ELF/DWARF
WARNING: possible compiler bug near offset 76255. in file
C:\eCosTools\MyTest\hello.elf (use DUMP)
WARNING: possible compiler bug near offset 77253. in file
C:\eCosTools\MyTest\hello.elf (use DUMP)
error: entry near offset 77392. in file C:\eCosTools\MyTest\hello.elf
(use DUMP)
The actual code seems to be loaded OK, but there are no symbols at all.
The mentioned offsets in the file are somewhere in the middle of the
DWARF2 segment.
After contact with Lauterbach, they claim that GCC generates broken
debug information, and this whas not the first time they've seen this. A
direct quote from the response is
"The file "hello" has a wrong abbreviation table (wrong DWARF2 debug
info)."
Now, how do I fix this? Is it perhaps already fixed by someone, or is it
beeing fixed? If not, where can I find enough information on DWARF2 so
that I can spot the errors? Also, what files in GCC contains potential
causes of the error (some are quite obvious, as their names contains
"dwarf", but any others)?
--
Lars Malmborg
Software Design
Precise Biometrics AB Phone: +46-46-286 57 61
Scheelevägen 15 Fax: +46-46-286 57 62
SE-223 70 Lund
Sweden
next reply other threads:[~1999-06-09 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-09 1:05 Lars Malmborg [this message]
1999-06-09 11:14 ` Jonathan Larmour
1999-06-10 14:05 ` Bob Cousins
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=375E2011.F29E60C2@precisebiometrics.com \
--to=lars.malmborg@precisebiometrics.com \
--cc=ecos-discuss@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).