public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: aaa@bbb.ccc.ddd (Andrew Wallace)
To: help-gcc@gnu.org
Subject: gcc-gethostbyaddr memory leak
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <82peet$l1r$1@perki.connect.com.au> (raw)
Message-ID: <19991231222400.kY0SDv4E945U_Cts0HlYzcF4IVensA65uSEOi98FF_g@z> (raw)

I hope this is the correct list, this looks like a gcc problem.  I don't think 
it's a programming question.

The following code leaks when it is passed an address that it cannot find.  If 
anybody has any suggestions I would appreciate any help.

Thanks,

Andrew

System info:
gcc version 2.95.1 19990816
Linux Redhat v6.0, I'm sorry I can't find the kernel version



// simple program to demo the leak in gethostbyaddr when a 
// name is not found


#include <netdb.h>
#include <sys/socket.h>
#include <errno.h>
#include <netinet/in.h>
#include <arpa/inet.h>



char* GetAddrName(char* clean_address)
{
  static int init_state;
  struct in_addr ip;

  if (inet_aton(clean_address, &ip))
  { 
    struct hostent* hostinfo = gethostbyaddr((char*)&ip, sizeof(ip), AF_INET);

    if (hostinfo)
      return hostinfo->h_name;

    if (h_errno != 1)   // display anything but HOST NOT FOUND 
      printf("ERROR: gethostbyaddr (%s,%d)(%s,%d)(%s)\n", 
          hstrerror(h_errno), h_errno, strerror(errno), errno, clean_address);

  }  // if

  else
    printf("ERROR: address seems invalid: %s\n", clean_address);

  return NULL;
}



int main(int argc, char** argv)
{
  int x;
  char buff[124];

  for (x = 0; x < 50000; x++)
  {
    sprintf(buff,"%d.%d.%d.%d",210,10,3, (random()%254) + 1); 

    printf("%-20.20s %s\n", GetAddrName(buff), buff);
    if (!(x % 100)) 
      sleep(1);
  }
}


             reply	other threads:[~1999-12-31 22:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-09 15:37 Andrew Wallace [this message]
1999-12-09 18:14 ` Arthur Gold
1999-12-31 22:24   ` Arthur Gold
1999-12-31 22:24 ` Andrew Wallace

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='82peet$l1r$1@perki.connect.com.au' \
    --to=aaa@bbb.ccc.ddd \
    --cc=help-gcc@gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).