From: Mark Kettenis <kettenis@wins.uva.nl>
To: msnyder@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix i386 FPU register conversion code
Date: Sat, 28 Jul 2001 13:53:00 -0000 [thread overview]
Message-ID: <200107282053.f6SKrMn19253@delius.kettenis.local> (raw)
In-Reply-To: <3B6316FC.7D86@redhat.com>
Date: Sat, 28 Jul 2001 12:48:12 -0700
From: Michael Snyder <msnyder@redhat.com>
Mark Kettenis wrote:
>
> Fixing the debug register number mapping scheme uncovered a bug in
> i386-tdep.c:i386_register_convert_to_virtual(). Fixed with the
> attached patch.
>
> Mark
Isn't "gdb_assert" rather strong for this use?
Seems like simply returning without doing anything
would be sufficient in case we were called with an
integer register or what-not. Calling gdb_assert
will result in the user being asked if he would like
GDB to abort and dump core (I think...)
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.
The assertion in i386_register_convert_to_raw() still seems
appropriate though.
Mark
next prev parent reply other threads:[~2001-07-28 13:53 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 [this message]
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
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=200107282053.f6SKrMn19253@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--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