Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: jkingdon@engr.sgi.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Fix Irix core dumps
Date: Mon, 19 Feb 2001 17:08:00 -0000	[thread overview]
Message-ID: <3A91C2EF.83BB492F@cygnus.com> (raw)
In-Reply-To: <200102092321.SAA05354@panix3.panix.com>

jkingdon@engr.sgi.com wrote:
> 
> Reading a core dump on Irix has bit-rotted some time since GDB 4.18
> (which works).  The culprit has to do with the size of the floating
> point registers (which thus affects all the registers after them in
> the registers array).  The enclosed fix does enable GDB to read Irix
> core dumps and doesn't look too hideous to me.  But I'd welcome
> suggestions if there is a better way.
> 
> I also had to make a straightforward fix to bfd/irix-core.c; I'll be
> sending that one to the binutils list.
> 
> 2001-02-09  Jim Kingdon  <jkingdon@engr.sgi.com>
> 
>         * mips-tdep.c (mips_register_raw_size): If FP_REGISTER_DOUBLE,
>         then floating point registers are 8 bytes.

I'm checking this in (indented slightly different) (just got to wait for
a build).
I'm pretty sure it will affect GDBs ability to communicate with some
obscure remote target (what register_raw_size() returns changed :-/)
however, as it was it was certainly wrong.

Thanks!
	Andrew

PS: Have I ever mentioned my desire to completly separate remote.c from
register_raw_size() and instead have something outside of GDB specifying
what a packet looks like? :-)


> Index: mips-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/mips-tdep.c,v
> retrieving revision 1.40
> diff -u -r1.40 mips-tdep.c
> --- mips-tdep.c 2001/02/08 06:03:53     1.40
> +++ mips-tdep.c 2001/02/09 22:59:43
> @@ -420,7 +420,15 @@
>    if (mips64_transfers_32bit_regs_p)
>      return REGISTER_VIRTUAL_SIZE (reg_nr);
>    else
> -    return MIPS_REGSIZE;
> +    {
> +      /* For MIPS_ABI_N32 (for example) we need 8 byte floating point
> +         registers.  */
> +      if (reg_nr >= FP0_REGNUM && reg_nr < FP0_REGNUM+32
> +         && FP_REGISTER_DOUBLE)
> +       return 8;
> +
> +      return MIPS_REGSIZE;
> +    }
>  }
> 
>  int


  reply	other threads:[~2001-02-19 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-09 15:23 jkingdon
2001-02-19 17:08 ` Andrew Cagney [this message]
2001-02-20 17:07   ` Jim Kingdon

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=3A91C2EF.83BB492F@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jkingdon@engr.sgi.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