All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Thiemo Seufer <ths@networkno.de>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
	linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH] use generic DWARF_DEBUG
Date: Wed, 10 May 2006 08:50:42 -0400	[thread overview]
Message-ID: <20060510125042.GA2666@nevyn.them.org> (raw)
In-Reply-To: <20060510071937.GA7813@networkno.de>

On Wed, May 10, 2006 at 08:19:37AM +0100, Thiemo Seufer wrote:
> Atsushi Nemoto wrote:
> > When debugging a kernel compiled by gcc 4.1 with gdb 6.4, gdb could
> > not show filename, linenumber, etc.  It seems fixed if I used generic
> > DWARF_DEBUG macro.  Although gcc 3.x seems work without this change,
> > it would be better to use the generic macro unless there were
> > something MIPS specific.
> 
> There was something MIPS specific for n64 (DWARF64) uuntil very
> recently. GCC HEAD switched n64 Linux to DWARF32 some days ago.

Shouldn't affect this.  What Atsushi is deleting are sections for DWARF
_1_, not DWARF _2_; that's ancient history.  I don't know why they need
to be listed at all, though; I've never had a problem, and orphan
placement ought to take care of it.

-- 
Daniel Jacobowitz
CodeSourcery

  parent reply	other threads:[~2006-05-10 12:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  6:36 [PATCH] use generic DWARF_DEBUG Atsushi Nemoto
2006-05-10  7:19 ` Thiemo Seufer
2006-05-10  7:56   ` Atsushi Nemoto
2006-05-10 11:24     ` Thiemo Seufer
2006-05-10 15:41       ` Atsushi Nemoto
2006-05-10 12:50   ` Daniel Jacobowitz [this message]
2006-05-10 14:08     ` Ralf Baechle
2006-05-10 14:57 ` Ralf Baechle

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=20060510125042.GA2666@nevyn.them.org \
    --to=dan@debian.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=ths@networkno.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.