Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@gnu.org>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Ada-valprint.c const tweaks
Date: Fri, 28 Jan 2005 20:13:00 -0000	[thread overview]
Message-ID: <200501282013.j0SKDbjU001907@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <41FA9054.8050909@gnu.org> (message from Andrew Cagney on Fri, 28 Jan 2005 14:19:48 -0500)

   Date: Fri, 28 Jan 2005 14:19:48 -0500
   From: Andrew Cagney <cagney@gnu.org>

   FYI,
   Andrew

This patch must be wrong!  In C a string has type 'char *' and the
type of a single character is 'int'.  If your compiler is warning
about incompatible types here, it's got a bug.  This proves that
mindless replacement of 'char' with 'bfd_byte' is a stupid thing to
do.  Please stop it *right* now.

Mark

   2005-01-28  Andrew Cagney  <cagney@gnu.org>

	   * ada-valprint.c (char_at, printstr): Make buffer a const bfd_byte.

   Index: ada-valprint.c
   ===================================================================
   RCS file: /cvs/src/src/gdb/ada-valprint.c,v
   retrieving revision 1.17
   diff -p -u -r1.17 ada-valprint.c
   --- ada-valprint.c	12 Jan 2005 18:31:30 -0000	1.17
   +++ ada-valprint.c	28 Jan 2005 19:16:03 -0000
   @@ -1,7 +1,7 @@
    /* Support for printing Ada values for GDB, the GNU debugger.
   +
       Copyright 1986, 1988, 1989, 1991, 1992, 1993, 1994, 1997, 2001,
   -   2002, 2003, 2004.
   -             Free Software Foundation, Inc.
   +   2002, 2003, 2004, 2005 Free Software Foundation, Inc.

    This file is part of GDB.

   @@ -278,7 +278,7 @@ ada_emit_char (int c, struct ui_file *st
       or 2) of a character.  */

    static int
   -char_at (char *string, int i, int type_len)
   +char_at (const bfd_byte *string, int i, int type_len)
    {
      if (type_len == 1)
	return string[i];
   @@ -439,8 +439,8 @@ ada_print_scalar (struct type *type, LON
     */

    static void
   -printstr (struct ui_file *stream, char *string, unsigned int length,
   -	  int force_ellipses, int type_len)
   +printstr (struct ui_file *stream, const bfd_byte *string,
   +	  unsigned int length, int force_ellipses, int type_len)
    {
      unsigned int i;
      unsigned int things_printed = 0;


  reply	other threads:[~2005-01-28 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 19:20 Andrew Cagney
2005-01-28 20:13 ` Mark Kettenis [this message]
2005-01-28 20:25   ` Andrew Cagney
2005-01-28 21:00     ` 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=200501282013.j0SKDbjU001907@elgar.sibelius.xs4all.nl \
    --to=kettenis@gnu.org \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@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