Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Dave Johnson <djohnson+linuxmips@sw.starentnetworks.com>,
	Daniel Jacobowitz <dan@debian.org>,
	linux-mips@linux-mips.org
Subject: Re: gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?
Date: Wed, 18 Jan 2006 15:51:17 +0000	[thread overview]
Message-ID: <20060118155117.GA17343@linux-mips.org> (raw)
In-Reply-To: <20060118154319.GA25368@deprecation.cyrius.com>

On Wed, Jan 18, 2006 at 03:43:19PM +0000, Martin Michlmayr wrote:

> > > -#if CONFIG_MIPS64
> > > +#if defined(CONFIG_MIPS64) && !defined(WANT_COMPAT_REG_H)
> 
> Obviously, this should be CONFIG_64BIT now.

That was a GDB bug so no need for kernel changes.

  Ralf

      reply	other threads:[~2006-01-18 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 21:08 gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed? Dave Johnson
2005-08-28 15:45 ` Daniel Jacobowitz
2006-01-16 16:09 ` Martin Michlmayr
2006-01-18 15:43   ` Martin Michlmayr
2006-01-18 15:51     ` Ralf Baechle [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=20060118155117.GA17343@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=dan@debian.org \
    --cc=djohnson+linuxmips@sw.starentnetworks.com \
    --cc=linux-mips@linux-mips.org \
    --cc=tbm@cyrius.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