public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: jlarmour@cygnus.co.uk (Jonathan Larmour)
To: lars.malmborg@precisebiometrics.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Trace32 running eCos
Date: Wed, 09 Jun 1999 11:14:00 -0000	[thread overview]
Message-ID: <199906091813.TAA13256@peshwari.cygnus.co.uk> (raw)
In-Reply-To: <375E2011.F29E60C2@precisebiometrics.com>

In article < 375E2011.F29E60C2@precisebiometrics.com > you write:
>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)
>[snip]
>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)?

If this is the case, you may want to ask on egcs@egcs.cygnus.com where
there should be a few more ARM toolchains experts to help :-).

Something else to try is to look at the output of arm-elf-readelf on the
executable to see if it reveals any more information.

Jifl
-- 
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK.  Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
 my brains kept falling out."    || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/  These opinions are all my own fault

  reply	other threads:[~1999-06-09 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-09  1:05 Lars Malmborg
1999-06-09 11:14 ` Jonathan Larmour [this message]
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=199906091813.TAA13256@peshwari.cygnus.co.uk \
    --to=jlarmour@cygnus.co.uk \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=lars.malmborg@precisebiometrics.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).