From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: Bizarre internal errors in regcache
Date: Mon, 26 Aug 2002 13:54:00 -0000 [thread overview]
Message-ID: <20020826205509.GB12224@nevyn.them.org> (raw)
In-Reply-To: <200208262028.g7QKS88T001023@elgar.kettenis.dyndns.org>
On Mon, Aug 26, 2002 at 10:28:08PM +0200, Mark Kettenis wrote:
> Date: Mon, 26 Aug 2002 15:52:47 -0400
> From: Daniel Jacobowitz <drow@mvista.com>
>
> On Mon, Aug 26, 2002 at 02:56:39PM -0400, Daniel Jacobowitz wrote:
> > I see this error on my laptop but not on my desktop; both current trees,
> > both rebuilt from scratch, both i386-linux. Any ideas?
>
> [ snip ]
>
> My desktop has SSE, my laptop doesn't, it seems. We can't call
> supply_register on an MMX register if we don't have any.
> dummy_sse_registers seems to be the culprit.
>
> Hmm, and my desktop sort of pretends it has the SSE registers.
>
> Anyway, I'm pretty certain that the problem is caused by the fact that
> the binary produced by the gdb.asm test isn't branded. Therefore GDB
> doesn't select the Linux OS/ABI but the generic OS/ABI which doesn't
> include the SSE regs. Since you're running on Linux, the native code
> tries to supply these registers anyway. i387_supply_fxsave() does
> deal with this gracefully, but dummy_sse_regs() doesn't.
>
> Can you try the attached patch?
That patch does it for me. This also shows up on core dumps, if you
don't include a binary, which is where I first noticed it.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-26 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 11:55 Daniel Jacobowitz
2002-08-26 12:51 ` Daniel Jacobowitz
2002-08-26 13:28 ` Mark Kettenis
2002-08-26 13:54 ` Daniel Jacobowitz [this message]
2002-09-01 15:12 ` [PATCH] " Mark Kettenis
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=20020826205509.GB12224@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@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