Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Alexandre Oliva <aoliva@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: GDB CVS won't build on OSF4.0's cc
Date: Tue, 29 May 2001 09:30:00 -0000	[thread overview]
Message-ID: <1010529163000.ZM28156@ocotillo.lan> (raw)
In-Reply-To: <org0dofodw.fsf@guarana.lsd.ic.unicamp.br>

On May 29,  7:19am, Alexandre Oliva wrote:

> 	* symfile.c (compare_psymbols, compare_symbols): Declare using
> 	PTR, as in the definition.
> 
> Index: gdb/symfile.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/symfile.c,v
> retrieving revision 1.32
> diff -u -p -r1.32 symfile.c
> --- gdb/symfile.c 2001/05/10 15:33:21 1.32
> +++ gdb/symfile.c 2001/05/29 10:18:16
> @@ -117,9 +117,9 @@ static void add_shared_symbol_files_comm
>  
>  static void cashier_psymtab (struct partial_symtab *);
>  
> -static int compare_psymbols (const void *, const void *);
> +static int compare_psymbols (const PTR, const PTR);
>  
> -static int compare_symbols (const void *, const void *);
> +static int compare_symbols (const PTR, const PTR);
>  
>  bfd *symfile_bfd_open (char *);

I'm not the maintainer of the file in question, but one of our long
term goals has been the elimination of PTR from the gdb sources.  I
think the fix should have been to change PTR in the definition to
void * rather than change the declaration to match the definition.

Kevin


  parent reply	other threads:[~2001-05-29  9:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29  3:20 Alexandre Oliva
2001-05-29  3:42 ` Alexandre Oliva
2001-05-29  4:12   ` Alexandre Oliva
2002-03-06 16:12     ` Alexandre Oliva
2002-03-06 17:58       ` Andrew Cagney
2002-03-06 18:52         ` Alexandre Oliva
2002-03-13 11:19           ` Alexandre Oliva
2002-03-25  8:43           ` Alexandre Oliva
2001-06-06 13:20   ` Elena Zannoni
2001-06-09 16:14     ` Alexandre Oliva
     [not found]       ` <Pine.SUN.3.91.1010610111224.5638I-100000@is>
2001-06-10 14:25         ` Alexandre Oliva
2001-06-11  1:06           ` Eli Zaretskii
2001-06-11  1:33             ` Russ Allbery
2001-06-11  7:04               ` Andrew Cagney
2001-06-11  6:32         ` Elena Zannoni
2001-06-11  6:34       ` Elena Zannoni
2002-03-06 16:36         ` Alexandre Oliva
2002-03-13 11:19           ` Alexandre Oliva
2002-03-19  9:41           ` Elena Zannoni
2002-03-19 10:31             ` Alexandre Oliva
2002-03-19 10:48               ` Elena Zannoni
2002-03-19 18:23                 ` Alexandre Oliva
2002-03-19 18:39                   ` Andrew Cagney
2002-03-19 20:40                     ` Elena Zannoni
2002-03-20  0:00                       ` Alexandre Oliva
2002-03-20  7:08                         ` Elena Zannoni
2002-03-19 23:43                     ` Alexandre Oliva
2002-03-20  7:10                       ` Elena Zannoni
2002-03-20 14:27                         ` Alexandre Oliva
2002-03-25  8:49                 ` Alexandre Oliva
2001-05-29  9:30 ` Kevin Buettner [this message]
2001-05-30 19:54   ` Alexandre Oliva

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=1010529163000.ZM28156@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=aoliva@redhat.com \
    --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