Re: gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Martin Michlmayr <tbm@xxxxxxxxxx>
Subject: Re: gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?
From: Ralf Baechle <ralf@xxxxxxxxxxxxxx>
Date: Wed, 18 Jan 2006 15:51:17 +0000
Cc: Dave Johnson <djohnson+linuxmips@xxxxxxxxxxxxxxxxxxxxxx>, Daniel Jacobowitz <dan@xxxxxxxxxx>, linux-mips@xxxxxxxxxxxxxx
In-reply-to: <20060118154319.GA25368@xxxxxxxxxxxxxxxxxxxxxx>
References: <17162.16068.212165.340275@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20050828154530.GA26423@xxxxxxxxxxxxxx> <17162.16068.212165.340275@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20060116160925.GE28383@xxxxxxxxxxxxxxxxxxxxxx> <20060118154319.GA25368@xxxxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.4.2.1i

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

References:
- gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?
  - From: Dave Johnson
- Re: gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?
  - From: Daniel Jacobowitz
- Re: gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?
  - From: Martin Michlmayr
- Re: gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?
  - From: Martin Michlmayr

Prev by Date: Re: gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?
Next by Date: Re: [PATCH Cobalt 1/1] 64-bit fix
Previous by thread: Re: gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?
Next by thread: ERROR regarding undefined reference to `__rpc_thread_svc_fdset'
Index(es):
- Date
- Thread

[Index of Archives] [Linux MIPS Home] [LKML Archive] [Linux ARM Kernel] [Linux ARM] [Linux] [Git] [Yosemite News] [Linux SCSI] [Linux Hams]

Powered by Linux