From: Jonathan Larmour <jlarmour@redhat.com>
To: Tim Michals <tim@cygnetinc.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] MIPS GDB information
Date: Tue, 13 Mar 2001 13:12:00 -0000 [thread overview]
Message-ID: <3AAE8D39.C18BF32@redhat.com> (raw)
In-Reply-To: <001d01c0ac00$d3dc46e0$d301010a@cygnetinc.com>
Tim Michals wrote:
>
> Jifl,
>
> Here's what I have:
>
> C:\idtCygnet\build>mips-elf-objdump -h boot.exe
> [snip]
It does indeed look like you've got no debug info. Odd. The most obvious
thing to try is building with alternatives like -ggdb or -gdwarf-2
After that, in your gcc sources edit gcc/config/mips/elf.h and change this:
#ifndef PREFERRED_DEBUGGING_TYPE
#define PREFERRED_DEBUGGING_TYPE DBX_DEBUG
#endif
to:
#define DWARF2_DEBUGGING_INFO
#define PREFERRED_DEBUGGING_TYPE DWARF2_DEBUG
Also try adding this to elf.h:
/* For the 'preferred' cases ("gN" and "ggdbN") we need to tell the
gnu assembler not to generate debugging information. */
#define SUBTARGET_ASM_DEBUGGING_SPEC "\
%{!mmips-as: \
%{g:-g0} %{g0:-g0} %{g1:-g0} %{g2:-g0} %{g3:-g0} \
%{ggdb:-g0} %{ggdb0:-g0} %{ggdb1:-g0} %{ggdb2:-g0} %{ggdb3:-g0} \
%{gdwarf-2*:-g0}} \
%{gstabs:-g} %{gstabs0:-g0} %{gstabs1:-g1} %{gstabs2:-g2} %{gstabs3:-g3} \
%{gstabs+:-g} %{gstabs+0:-g0} %{gstabs+1:-g1} %{gstabs+2:-g2}
%{gstabs+3:-g3} \
%{gcoff:-g} %{gcoff0:-g0} %{gcoff1:-g1} %{gcoff2:-g2} %{gcoff3:-g3}"
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
prev parent reply other threads:[~2001-03-13 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-07 14:20 Tim Michals
2001-03-13 12:16 ` Jonathan Larmour
2001-03-13 13:02 ` Tim Michals
2001-03-13 13:12 ` 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=3AAE8D39.C18BF32@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=tim@cygnetinc.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).