Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: gdb@cygnus.com
Subject: Re: More gdb-4.17.85 testresults
Date: Thu, 01 Apr 1999 00:00:00 -0000	[thread overview]
Message-ID: <36E86522.722EFB9B@cygnus.com> (raw)
In-Reply-To: <npaexm4p27.fsf.cygnus.gdb@zwingli.cygnus.com>

Jim Blandy wrote:
> Based on the responses from the ANSI C wonks, I think you're going to
> have to change the argument types in the prototypes.  Glancing over
> it, this doesn't look like a problem.

Below is a somewhat pragmatic patch to address the problem (assuming
that this weeks mailer doesn't eat several long lines :-).

The thing is that the function remote_query() is assigned to
`struct target_ops'.to_query.  If we're going to change the signature
of remote_query() then we'll also need to change to_query and any other
uses of it. (While there are not that many it does appear to be
excessive
effort for a problem that goes away in the next release).

I figure it is easier, for the 4.18 release, to just zap prototypes
when they create problems.

The below is for your aproval.

	Andrew

*** remote.c    1999/03/10 03:27:15     1.179
--- remote.c    1999/03/12 00:46:39
*************** static int ishex PARAMS ((int ch, int *v
*** 294,301 ****
  
  static int stubhex PARAMS ((int ch));
  
- static int remote_query PARAMS ((char, char *, char *, int *));
- 
  static int hexnumstr PARAMS ((char *, ULONGEST));
  
  static CORE_ADDR remote_address_masked PARAMS ((CORE_ADDR));
--- 294,299 ----
*************** char *unpack_varlen_hex PARAMS ((char *b
*** 315,322 ****
  static char *unpack_nibble PARAMS ((char *buf, int *val));
  
  static char *pack_nibble PARAMS ((char *buf, int nibble));
- 
- static char *pack_hex_byte PARAMS ((char *pkt, unsigned char byte));
  
  static char *unpack_byte PARAMS ((char *buf, int *value));
  
--- 313,318 ----


       reply	other threads:[~1999-04-01  0:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9903039205.AA920520366.cygnus.gdb@cc.pmsc.com>
     [not found] ` <npaexm4p27.fsf.cygnus.gdb@zwingli.cygnus.com>
1999-04-01  0:00   ` Andrew Cagney [this message]
1999-04-01  0:00 ` Andrew Cagney
1999-04-01  0:00   ` Jim Blandy
1999-04-01  0:00   ` Todd Whitesel
1999-04-01  0:00   ` Stan Shebs
1999-04-01  0:00   ` Mike Vermeulen
1999-04-01  0:00 rodneybrown

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=36E86522.722EFB9B@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb@cygnus.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