public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Chris Morrow <cmorrow@YottaYotta.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] mips_rm7000.ld and dwarf
Date: Fri, 03 Aug 2001 13:45:00 -0000	[thread overview]
Message-ID: <3B6B0D75.6DFAF4E0@redhat.com> (raw)
In-Reply-To: <3B6B0810.F8CD7E2C@YottaYotta.com>

Chris Morrow wrote:
> 
> Gdb (version 5.0) does not find any debugging symbols when
> attaching to an image produced with mips_rm7000.ld. If I copy
> debugging section stuff from the v1.3.1 linker script and remove
> the new stuff, gdb does find debugging symbols.
> 
> My guess is that a -gdwarf or one of the similar flags should
> be passed to gcc instead of just -g. I'm using gcc 2.96 and
> binutils  version 010326 (with BFD 010326)
> 
> Is this correct?

Or that debug info is broken in the tools you are using :-). What target
triple are you using for the tools? 

If you have a particular patch that you can verify works for you, we could
try it. Note that -gdwarf wouldn't be advisable because dwarf 1 has lousy
support for C++ debugging. -gdwarf-2 would be better, if that helps.

> Also how is gcc v3.0 working out?

I haven't reached any mips tools yet. I'm still testing the x86 due to some
internal difficulties.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

      reply	other threads:[~2001-08-03 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 22:09 [ECOS] please help me A Shobhan
2001-08-03  5:31 ` Jonathan Larmour
2001-08-03 12:27   ` A Shobhan
2001-08-03 12:41     ` Jonathan Larmour
2001-08-03 13:36     ` [ECOS] mips_rm7000.ld and dwarf Chris Morrow
2001-08-03 13:45       ` Jonathan Larmour [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=3B6B0D75.6DFAF4E0@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=cmorrow@YottaYotta.com \
    --cc=ecos-discuss@sourceware.cygnus.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).