From: Thomas Schwinge <tschwinge@gnu.org>
To: ams@gnu.org
Cc: gdb-patches@sourceware.org, pedro@codesourcery.com
Subject: [gnu-nat] PATCH (part of PR #2534)
Date: Tue, 07 Oct 2008 23:11:00 -0000 [thread overview]
Message-ID: <20081007230843.GF7127@fencepost.gnu.org> (raw)
In-Reply-To: <E1KnHiN-0003nN-16@fencepost.gnu.org>
[-- Attachment #1: gdb-2-BAD_TYPECHECK.patch --]
[-- Type: text/plain, Size: 972 bytes --]
2008-10-06 Thomas Schwinge <tschwinge@gnu.org>
* reply_mig_hack.awk: Use the `BAD_TYPECHECK' macro.
Index: reply_mig_hack.awk
===================================================================
RCS file: /cvs/src/src/gdb/reply_mig_hack.awk,v
retrieving revision 1.6
diff -u -p -r1.6 reply_mig_hack.awk
--- reply_mig_hack.awk 1 Jan 2008 22:53:12 -0000 1.6
+++ reply_mig_hack.awk 6 Oct 2008 08:42:50 -0000
@@ -101,7 +101,7 @@ parse_phase == 5 && /^#if[ \t]TypeCheck/
# structure that we want to check for.
print "\tif (In0P->Head.msgh_size == sizeof (Reply)";
print "\t && ! (In0P->Head.msgh_bits & MACH_MSGH_BITS_COMPLEX)";
- print "\t && *(int *)&In0P->" arg_type_code_name[0] " == *(int *)&" arg_check_name[0];
+ print "\t && ! BAD_TYPECHECK(&In0P->" arg_type_code_name[0] ", &" arg_check_name[0] ")";
print "\t && In0P->" arg_name[0] " != 0)";
print "\t /* Error return, only the error code argument is passed. */";
print "\t {";
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2008-10-07 23:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 17:38 [gnu-nat] PATCH (part of PR #2534) s/current_inferior/gnu_current_inf/g Pedro Alves
2008-10-07 18:03 ` Alfred M. Szmidt
2008-10-07 18:51 ` Pedro Alves
2008-10-07 18:58 ` Alfred M. Szmidt
2008-10-07 23:11 ` Thomas Schwinge [this message]
2008-10-09 16:08 ` [gnu-nat] PATCH (part of PR #2534) Thomas Schwinge
2008-10-07 23:13 ` Thomas Schwinge
2008-10-09 16:09 ` Thomas Schwinge
2008-10-10 11:41 ` Alfred M. Szmidt
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=20081007230843.GF7127@fencepost.gnu.org \
--to=tschwinge@gnu.org \
--cc=ams@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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