Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Court <court@oz.agile.tv>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: Mark Kettenis <kettenis@science.uva.nl>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] The MIPS/Linux port
Date: Thu, 05 Jul 2001 16:57:00 -0000	[thread overview]
Message-ID: <3B44FEE6.2070506@oz.agile.tv> (raw)
In-Reply-To: <20010704163423.A25013@nevyn.them.org>

Daniel Jacobowitz wrote:

>On Wed, Jul 04, 2001 at 11:51:27PM +0200, Mark Kettenis wrote:
>
>>Looks like the MIPS port was started before a bit of reformatting of
>>the sources and conversion to ISO C took place.  Please
>>
>
><snip>
>
>Fixed.  Do you see any other formatting problems?
>
Hi Daniel,

You have a bug in your  supply_fpregset() and fill_fpregset()
routines.  You are being passed an elf_fpregset_t * and incrementing
the counter by 264 od bytes each time through the loops.  You
need to offload the arguement something like the following before
using it with regi.

  elf_fpreg_t  *fpregp = &(*fpregsetp)[0];


This wont show up very well until you try and load a core dump
files which will actually cause gdb to die as it spins off into invalid
memory.    I would be surprised if your floating point regs in
gdb look any good the way the code is at the moment.
I had to look at the assembler to work this out a few days ago.

Cheers

John Court


  parent reply	other threads:[~2001-07-05 16:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010704121952.A17445@nevyn.them.org>
2001-07-04 14:51 ` H . J . Lu
2001-07-04 14:53 ` Mark Kettenis
2001-07-04 16:34   ` Daniel Jacobowitz
2001-07-05  2:12     ` Mark Kettenis
2001-07-05 16:57     ` John Court [this message]
2001-07-05 17:30       ` Daniel Jacobowitz
2001-07-05 17:45         ` John Court
2001-07-05 17:48           ` Daniel Jacobowitz
2001-07-04 23:48 ` Eli Zaretskii

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=3B44FEE6.2070506@oz.agile.tv \
    --to=court@oz.agile.tv \
    --cc=dmj+@andrew.cmu.edu \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@science.uva.nl \
    /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