From: Daniel Jacobowitz <drow@false.org>
To: Stephane Lambert <stephane.lambert@cortus.com>
Cc: gdb@sourceware.org
Subject: Re: FATAL: vmlinux is truncated
Date: Mon, 19 May 2008 12:30:00 -0000 [thread overview]
Message-ID: <20080519122934.GA446@caradoc.them.org> (raw)
In-Reply-To: <483146F6.2070208@cortus.com>
On Mon, May 19, 2008 at 11:23:02AM +0200, Stephane Lambert wrote:
> Hello all,
> I'm porting uclinux on the Cortus Aps3 Processeur. When I compile, I
> obtain a FATAL error: vmlinux is truncated.
> I've done several tries by modifying the vmlinux script (vmlinux.lds.S)
> and finally I can fix the problem by removing the Heap section.So it's
> seems this error is a vmlinux script problem. But I would like to
> understand what is happening to avoid this problem after, and what this
> error really means, and add my Heap section correcly.
> Could someone help me please?
Sorry, this has nothing to do with GDB.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-05-19 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 9:30 Stephane Lambert
2008-05-19 12:30 ` Daniel Jacobowitz [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=20080519122934.GA446@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=stephane.lambert@cortus.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