From: Mark Kettenis <kettenis@wins.uva.nl>
To: msnyder@redhat.com
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix i386 FPU register conversion code
Date: Mon, 30 Jul 2001 14:42:00 -0000 [thread overview]
Message-ID: <200107302124.f6ULOrq08573@delius.kettenis.local> (raw)
In-Reply-To: <3B659A3C.6B29011@cygnus.com>
Date: Mon, 30 Jul 2001 10:32:44 -0700
From: Michael Snyder <msnyder@cygnus.com>
Andrew Cagney wrote:
>
> > Hmm, when I added the assertion, I was under the impression that if
> > the virtual type wasn't a floating-point type it would be a GDB
> > internal error, hence the gdb_assert. However, this is probably not
> > entirely true, since I now think that bogus debug information (e.g. a
> > stab that says that an integer variable that lives in a
> > floating-point register) might trip the assertion. Printing a warning
> > and returning without doing anything is probably better.
>
> By ``nothing'' I guess you mean do something like zero the destination
> buffer :-)
Right. Silently fix it up, rather than call abort.
Some errors don't warrant terminating a possibly long
debug session.
I attached should address the concerns of both of you. Checked in on
head and branch.
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* i386-tdep.c (i386_register_convert_to_virtual): Replace
assertion with a warning if we're asked to convert towards a
non-floating-point type. Zero out the the buffer where the data
is supposed to be stored in that case.
Index: i386-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/i386-tdep.c,v
retrieving revision 1.36
diff -u -p -r1.36 i386-tdep.c
--- i386-tdep.c 2001/07/28 17:03:38 1.36
+++ i386-tdep.c 2001/07/30 20:54:33
@@ -1046,7 +1046,13 @@ i386_register_convert_to_virtual (int re
DOUBLEST d;
/* We only support floating-point values. */
- gdb_assert (TYPE_CODE (type) == TYPE_CODE_FLT);
+ if (TYPE_CODE (type) != TYPE_CODE_FLT)
+ {
+ warning ("Cannot convert floating-point register value "
+ "to non-floating-point type.");
+ memset (to, 0, TYPE_LENGTH (type));
+ return;
+ }
/* First add the necessary padding. */
memcpy (buf, from, FPU_REG_RAW_SIZE);
prev parent reply other threads:[~2001-07-30 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 9:49 Mark Kettenis
2001-07-28 12:49 ` Michael Snyder
2001-07-28 13:53 ` Mark Kettenis
2001-07-30 10:35 ` Michael Snyder
[not found] ` <3B633A59.6030009@cygnus.com>
2001-07-30 10:36 ` Michael Snyder
2001-07-30 14:42 ` Mark Kettenis [this message]
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=200107302124.f6ULOrq08573@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.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