From: Andrew Cagney <ac131313@ges.redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com
Subject: Re: [rfa:i386] Add mmx registers
Date: Tue, 13 Aug 2002 15:03:00 -0000 [thread overview]
Message-ID: <3D59822D.9060302@ges.redhat.com> (raw)
In-Reply-To: <3D598055.1000308@ges.redhat.com>
> Date: Tue, 13 Aug 2002 10:35:37 -0400
> From: Andrew Cagney <ac131313@ges.redhat.com>
>
> > Hello,
> > > This adds mmx registers to the i386.
> >
> Done, this is what I committed.
>
> Ouch! This patch uncovers a problem in the new regcache code and
> segfaults on my FreeBSD 4.6-STABLE system. The problem is that:
>
> My Red Hat GNU/Linux tests didn't bat an eyelid :-(
>
> + set_gdbarch_pseudo_register_read (gdbarch, i386_pseudo_register_read);
> + set_gdbarch_pseudo_register_write (gdbarch, i386_pseudo_register_write);
>
> changes the i386 target's register cache from "legacy" to "new". This
> means that there isn't room for the pseudo registers in
> register_valid_p, yet registers_changed() tries to frob the entries
> for the pseudo registers.
>
> I don't see an obvious way to fix this. Any bright ideas Andrew?
>
> Hmm, yes. It should be clearing:
> [0 .. current_regcache->descr->nr_raw_registers)
PS: The code should also still allocate nr_cooked_registers worth of
register_valid_p. That way, erant code won't crash things.
I'll fix both in a tick.
Andrew
next prev parent reply other threads:[~2002-08-13 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 16:58 Andrew Cagney
2002-08-12 11:10 ` Mark Kettenis
2002-08-12 12:00 ` Andrew Cagney
2002-08-13 7:35 ` Andrew Cagney
2002-08-13 14:39 ` Mark Kettenis
2002-08-13 14:55 ` Andrew Cagney
2002-08-13 15:03 ` Andrew Cagney [this message]
2002-08-13 15:10 ` Mark Kettenis
2002-08-13 15:21 ` Andrew Cagney
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=3D59822D.9060302@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.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