Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Martin M. Hunt" <hunt@redhat.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] new tcp_open
Date: Thu, 20 Dec 2001 03:39:00 -0000	[thread overview]
Message-ID: <200112200816.AAA24102@cygnus.com> (raw)
In-Reply-To: <15393.6280.385863.67517@localhost.localdomain>

Those warnings were always there.  My patch reverted those lines back
to what was there before.  However, it does appear that changing the char * 
cast to a void * would eliminate the warning and should probably work 
everywhere.  Systems that based their sockets on very old BSD have char * 
instead of void * in their setsockopt prototypes.

I tested void * on Linux and Windows and neither complain.  I have been
trying all day on a Solaris box, but it just can't seem to compile
GDB in less than a couple of days.  How can a big Ultrasparc with
a load average of 0.08 take > 12 hours to build GDB???

Martin


On Wednesday 19 December 2001 02:45 pm, Elena Zannoni wrote:
> Martin, I am getting these warnings on solaris (with ,-Werror):
>
>
> cc1: warnings being treated as errors
> /es/scratch/ezannoni/uberbaum/src/gdb/ser-tcp.c: In function `tcp_open':
> /es/scratch/ezannoni/uberbaum/src/gdb/ser-tcp.c:154: warning: passing arg 4
> of `getsockopt' from incompatible pointer type make: *** [ser-tcp.o] Error
> 1
>
> Elena
>
> Martin M. Hunt writes:
>  > Checked in.
>  >
>  > Martin
>  >
>  > On Tuesday 18 December 2001 03:21 am, Andrew Cagney wrote:
>  > > > Please give this patch a try and see if it fixes the problem.
>  > > >
>  > > > Index: ser-tcp.c
>  > > > ===================================================================
>  > > > RCS file: /cvs/src/src/gdb/ser-tcp.c,v
>  > > > retrieving revision 1.9
>  > > > diff -u -p -r1.9 ser-tcp.c
>  > > > --- ser-tcp.c   2001/12/07 17:57:05     1.9
>  > > > +++ ser-tcp.c   2001/12/18 10:54:31
>  > > > @@ -165,6 +165,10 @@ tcp_open (struct serial *scb, const char
>  > > >    tmp = 0;
>  > > >    ioctl (scb->fd, FIONBIO, &tmp);
>  > > >
>  > > > +  tmp = 1;
>  > > > +  setsockopt (scb->fd, IPPROTO_TCP, TCP_NODELAY,
>  > > > +             (char *)&tmp, sizeof (tmp));
>  > > > +
>  > > >    /* If we don't do this, then GDB simply exits
>  > > >       when the remote side dies.  */
>  > > >    signal (SIGPIPE, SIG_IGN);
>  > >
>  > > If it does, feel free to check it, and any other related changes in
>  > > :-)
>  > >
>  > >
>  > > Andrew


  reply	other threads:[~2001-12-20 11:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 11:18 Martin M. Hunt
2001-12-03 12:02 ` Andrew Cagney
2001-12-03 13:26   ` Martin M. Hunt
2001-12-03 13:36     ` Andrew Cagney
2001-12-03 22:13       ` Martin M. Hunt
2001-12-18  2:41 ` Orjan Friberg
2001-12-18  2:57   ` Martin M. Hunt
2001-12-18  3:22     ` Andrew Cagney
2001-12-18 12:29       ` Martin M. Hunt
2001-12-19 15:32         ` Elena Zannoni
2001-12-20  3:39           ` Martin M. Hunt [this message]
2001-12-20  3:04             ` Andrew Cagney
2001-12-18  3:40     ` Orjan Friberg

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=200112200816.AAA24102@cygnus.com \
    --to=hunt@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=ezannoni@cygnus.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