public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Torsten Mohr <tmohr@s.netic.de>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: insight-6.0: error loading an ELF (target arm-unknown-elf)
Date: Thu, 20 Nov 2003 15:33:00 -0000	[thread overview]
Message-ID: <1069342643.1592.2.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <200311201448.49867.tmohr@s.netic.de>

On Thu, 2003-11-20 at 05:48, Torsten Mohr wrote:
> But insight-6.0 refuses to load the ELF (filename "main"):
> 
> Error loading "path/main":
>  bad offset (0x20206a6) in compilation unit header
> (offset 0x0 + 6) [in module /path/main]

[snip]

> I don't think the error is in insight, but i'm really
> interested in what this error message means, it doesn't
> mean anything to me at the moment.  As readelf and objcopy
> work fine, it might be some information in the debug
> sections?

You are absolutely correct. [How refreshing: someone who understands the
difference between insight and gdb!]

Given the language of the error message ("compilation unit header"), I
suspect your suspicions about the debug info are correct: there is an
error with gdb reading the dwarf debug info.

Your best route is to run this via the command line, take your testcase
and command line output, and bring it to the attention of the gdb folks:
gdb At sources. DoT readhat dOt com.

Good luck,
Keith


      reply	other threads:[~2003-11-20 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 14:02 Torsten Mohr
2003-11-20 15:33 ` Keith Seitz [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=1069342643.1592.2.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=tmohr@s.netic.de \
    /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).