public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: [PATCH] Update VALUE_CONTENTS and VALUE_EMBEDDED_OFFSET
Date: Tue, 08 Feb 2005 01:15:00 -0000	[thread overview]
Message-ID: <1107825340.5134.61.camel@lindt.uglyboxes.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 340 bytes --]

These two macros are now functions (of the same name, all lowercase).
I've checked in a patch which should fix the recent build problem
arising from this.

Keith

ChangeLog
2005-02-07  Keith Seitz  <kseitz@sources.redhat.com>

        * generic/gdbtk-cmds.c (gdb_eval): VALUE_EMBEDDED_OFFSET and
        VALUE_CONTENTS are now functions.



[-- Attachment #2: macro-update.patch --]
[-- Type: text/x-patch, Size: 855 bytes --]

Index: generic/gdbtk-cmds.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-cmds.c,v
retrieving revision 1.86
diff -u -p -r1.86 gdbtk-cmds.c
--- generic/gdbtk-cmds.c	18 Jan 2005 00:14:39 -0000	1.86
+++ generic/gdbtk-cmds.c	8 Feb 2005 01:11:49 -0000
@@ -622,8 +622,8 @@ gdb_eval (ClientData clientData, Tcl_Int
   /* "Print" the result of the expression evaluation. */
   stb = mem_fileopen ();
   make_cleanup_ui_file_delete (stb);
-  val_print (value_type (val), VALUE_CONTENTS (val),
-	     VALUE_EMBEDDED_OFFSET (val), VALUE_ADDRESS (val),
+  val_print (value_type (val), value_contents (val),
+	     value_embedded_offset (val), VALUE_ADDRESS (val),
 	     stb, format, 0, 0, 0);
   result = ui_file_xstrdup (stb, &dummy);
   Tcl_SetObjResult (interp, Tcl_NewStringObj (result, -1));

                 reply	other threads:[~2005-02-08  1:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1107825340.5134.61.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).