Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Mike Connors <mike.connors@ghs.com>
Cc: linux-mips@linux-mips.org
Subject: Re: assembly debug question
Date: Mon, 21 Apr 2003 09:19:19 -0400	[thread overview]
Message-ID: <20030421131919.GA26660@nevyn.them.org> (raw)
In-Reply-To: <001d01c306d2$a55fbe80$7c70a8c0@NOMAD>

On Sat, Apr 19, 2003 at 05:20:27PM -0700, Mike Connors wrote:
> Hi All, 
> 
> I'm using gcc v2.96 to compile a MIPS targeted Linux kernel 
> and am finding it difficult to produce debug information 
> for assembly files. 
> 
> I've discovered that a typical compile line for assembly 
> in the kernel gets its parameters from AFLAGS and results 
> in the following commandline: 
> 
> mipsel-linux-gcc -D__ASSEMBLY__ -D__KERNEL__ -I/l/include \
> 	-G 0 -mno-abicalls -fno-pic -mcpu=r4600 -mips2 \
> 	-Wa,--trap -pipe -c entry.S -o entry.o 
> 
> According to the documentation, some targets support 
> dwarf debug information using --gdwarf2.  Does anyone 
> know if the MIPS target is supported in version? 
> 
> Also, --gstabs doesn't seem to work either.  Nor does 
> -gdwarf-2, -gdwarf -g2, -gstabs+, -gdwarf+, etc. 
> 
> Has anyone had luck producing debug information for 
> assembly files with this version of gcc? 
> 
> ./mipsel-linux-gcc --version 
> 2.96 
> ./mipsel-linux-as --version 
> GNU assembler 2.11.92.0.10 

I think --gstabs is later than that version of binutils.  Also, I
didn't fix DWARF-2 for MIPS until well after those tools versions,
so I believe you won't be able to use that at all.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

      parent reply	other threads:[~2003-04-21 13:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-20  0:20 assembly debug question Mike Connors
2003-04-20  0:20 ` Mike Connors
2003-04-21 13:19 ` 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=20030421131919.GA26660@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mike.connors@ghs.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