Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michal Ludvig <mludvig@suse.cz>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] remote debugging patches
Date: Wed, 13 Mar 2002 11:09:00 -0000	[thread overview]
Message-ID: <3C8FA3FC.6040106@suse.cz> (raw)
In-Reply-To: <jebsds2w39.fsf@sykes.suse.de>

Andreas Schwab wrote:
> Maybe it's just me, but I hate arbitrary limits.  There is no need for
> sprintf at this point anyway.  I'd suggest to define another variable that
> either points to name or to the result of inet_ntoa and use that in the
> fprintf call.  No need for namebuf either.

OK, the 100-chars limit is removed and the patch is getting smaller and 
smaller :-)) Do you like it more this way, Andreas?
Index: gdbserver/remote-utils.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/remote-utils.c,v
retrieving revision 1.8
diff -c -3 -p -B -b -r1.8 remote-utils.c
*** remote-utils.c      2002/02/14 06:21:22     1.8
--- remote-utils.c      2002/03/13 19:05:33
*************** remote_open (char *name)
*** 99,105 ****
         }
   #endif

!
       }
     else
       {
--- 99,105 ----
         }
   #endif

!       fprintf (stderr, "Remote debugging using %s\n", name);
       }
     else
       {
*************** remote_open (char *name)
*** 154,159 ****
--- 154,163 ----

         signal (SIGPIPE, SIG_IGN);      /* If we don't do this, then 
gdbserver simply
                                            exits when the remote side 
dies.  */
+
+       /* Convert IP address to string.  */
+       fprintf (stderr, "Remote debugging from host %s\n",
+          inet_ntoa (sockaddr.sin_addr));
       }

   #if defined(F_SETFL) && defined (FASYNC)
*************** remote_open (char *name)
*** 164,170 ****
   #endif
   #endif
     disable_async_io ();
-   fprintf (stderr, "Remote debugging using %s\n", name);
   }

   void
--- 168,173 ----


  reply	other threads:[~2002-03-13 19:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-10 10:34 Michal Ludvig
2002-03-10 11:35 ` Daniel Jacobowitz
2002-03-10 11:43   ` Michal Ludvig
2002-03-10 14:30     ` Daniel Jacobowitz
2002-03-11  6:54       ` Michal Ludvig
2002-03-11  7:37         ` Daniel Jacobowitz
2002-03-11 18:22         ` Andrew Cagney
2002-03-11 18:47           ` Daniel Jacobowitz
2002-03-13  6:14             ` Michal Ludvig
2002-03-13  7:48               ` Andreas Schwab
2002-03-13  8:17                 ` Michal Ludvig
2002-03-13  8:34                   ` Andrew Cagney
2002-03-13  9:53                   ` Andreas Schwab
2002-03-13 11:09                     ` Michal Ludvig [this message]
2002-03-13 12:24                       ` Andreas Schwab
2002-03-13  9:07               ` Daniel Jacobowitz
2002-03-10 12:16 ` Andrew Cagney
2002-03-11  7:08   ` Michal Ludvig
2002-03-11  7:37     ` Daniel Jacobowitz
2002-03-11  8:06       ` Michal Ludvig
2002-03-11  8:12         ` Daniel Jacobowitz
2002-03-11  8:38           ` Michal Ludvig
2002-03-11  8:34         ` Andrew Cagney
2002-03-11  7:53     ` Andrew Cagney
2002-03-11  9:12       ` Michal Ludvig

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=3C8FA3FC.6040106@suse.cz \
    --to=mludvig@suse.cz \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    /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