From: Daniel Jacobowitz <drow@false.org>
To: Yi Sun <ysun@juniper.net>
Cc: gdb@sources.redhat.com
Subject: Re: -ffunction-sections and gdb
Date: Wed, 27 Jul 2005 18:10:00 -0000 [thread overview]
Message-ID: <20050727181046.GB14088@nevyn.them.org> (raw)
In-Reply-To: <F07F17B61B7FF545BC7D7E4BFBE15D2A01776C55@hadron.jnpr.net>
On Wed, Jul 27, 2005 at 11:05:22AM -0700, Yi Sun wrote:
> Hi,
>
> I have some code built with -ffunction-sections and running on a mip64
> embedded platform. My code can be booted and ran. But when I'm using
> list command in gdb with my image, gdb complains "no source file for
> address". I'm using gdb 5.0 and it configured as
> "--host=sparc-sun-solaris2.6 --target=mips". My gcc is "gcc version
> 2.9-gnupro-99r1".
>
> Gcc manual said that if you use -ffunction-sections, gdb may not work.
>
> My question is:
>
> Is there a fix or workaround for this problem?
Sorry, but that version of GDB is so old that we can't help you with
it. You may want to try a more recent version of GDB.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-27 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 18:05 Yi Sun
2005-07-27 18:10 ` Daniel Jacobowitz [this message]
2005-07-27 22:29 Yi Sun
2005-07-28 4:11 ` Ramana Radhakrishnan
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=20050727181046.GB14088@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ysun@juniper.net \
/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).