From: Martin Michlmayr <tbm@cyrius.com>
To: Dave Johnson <djohnson+linuxmips@sw.starentnetworks.com>,
Daniel Jacobowitz <dan@debian.org>
Cc: 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:43:19 +0000 [thread overview]
Message-ID: <20060118154319.GA25368@deprecation.cyrius.com> (raw)
In-Reply-To: <20060116160925.GE28383@deprecation.cyrius.com>
* Martin Michlmayr <tbm@cyrius.com> [2006-01-16 16:09]:
> Can this be applied?
>
>
> > Fix o32 core files under 64bit kernel to use correct register
> > offset in NT_PRSTATUS
> > Signed-off-by: Dave Johnson <djohnson+linuxmips@sw.starentnetworks.com>
> >
> > -#if CONFIG_MIPS64
> > +#if defined(CONFIG_MIPS64) && !defined(WANT_COMPAT_REG_H)
Obviously, this should be CONFIG_64BIT now.
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2006-01-18 15:41 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 [this message]
2006-01-18 15:51 ` 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=20060118154319.GA25368@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=dan@debian.org \
--cc=djohnson+linuxmips@sw.starentnetworks.com \
--cc=linux-mips@linux-mips.org \
/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.