Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remove unused declaration in top.c
Date: Thu, 17 May 2001 08:02:00 -0000	[thread overview]
Message-ID: <15107.59402.14923.412770@kwikemart.cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010517174634.14151E-100000@is>

Eli Zaretskii writes:
 > I'm asking for approval of the following patch which removes an unused 
 > definition of struct user_args variable in top.c.  AFAICS, this is a 
 > relic left behind when cli-* files were separated from top.c.  The reason 
 > I payed attention to it was that the Irix linker printed a warning about 
 > duplicate definition (one in top.c, the other in cli-script.c).
 > 
 > Okay to commit?  (It looks like an obvious fix, but...)
 > 

Yes, thanks!

Elena



 > 2001-05-17  Eli Zaretskii  <eliz@is.elta.co.il>
 > 
 > 	* top.c (user_args): Remove unused declaration.
 > 
 > 
 > --- gdb/top.c~	Thu Apr  5 18:59:30 2001
 > +++ gdb/top.c	Thu May 17 17:36:24 2001
 > @@ -224,21 +224,6 @@
 >  /* Level of control structure.  */
 >  static int control_level;
 >  
 > -/* Structure for arguments to user defined functions.  */
 > -#define MAXUSERARGS 10
 > -struct user_args
 > -  {
 > -    struct user_args *next;
 > -    struct
 > -      {
 > -	char *arg;
 > -	int len;
 > -      }
 > -    a[MAXUSERARGS];
 > -    int count;
 > -  }
 > - *user_args;
 > -
 >  /* Signal to catch ^Z typed while reading a command: SIGTSTP or SIGCONT.  */
 >  
 >  #ifndef STOP_SIGNAL
 > 


  reply	other threads:[~2001-05-17  8:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-17  7:51 Eli Zaretskii
2001-05-17  8:02 ` Elena Zannoni [this message]
2001-05-17  8:06   ` Eli Zaretskii

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=15107.59402.14923.412770@kwikemart.cygnus.com \
    --to=ezannoni@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --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