From: Keith Seitz <keiths@redhat.com>
To: Himansu Doshi <rocder@hotmail.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: insight errors....
Date: Wed, 21 Jan 2004 14:46:00 -0000 [thread overview]
Message-ID: <1074696687.1588.12.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <BAY7-F117VMUnLMdRKa000199a4@hotmail.com>
On Sat, 2004-01-10 at 02:13, Himansu Doshi wrote:
> I am compiling u-boot for at91rm9200dk board. I am using insight for
> debugging and cross compiler for arm from insight to compile the source. I
> am able to compile all the files properly. However when the linking take
> place I get an error for the libgcc.a file. The error is as follows----
This error, of course, has nothing to do with insight. Please ask the
gcc folk for help on this.
> error loading "/Himansu/u-boot-1.0.0/u-boot bad offset (0x2011eb2f) in
> compilation unit header (offset 0x0 + 6) [in module
> /Himansu/u-boot-1.0.0/u-boot]
This is not something that Insight would tell a user -- it's a gdb
error. I suggest reproducing the problem with gdb and sending a note to
the gdb folks for resolution.
Keith
prev parent reply other threads:[~2004-01-21 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 10:13 Himansu Doshi
2004-01-21 14:46 ` 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=1074696687.1588.12.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=rocder@hotmail.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).