From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

Description of problem:
Just calling gethostbyname in a program and running it with mudflap on reports 57 memory leaks. The number of leaks reported in Fedora Core 3, the previous version, is 58, one more ;).

Version-Release number of selected component (if applicable):
glibc-2.3.5-10

How reproducible:
Always

Steps to Reproduce:
1. Create a file main.cpp / main.c with the following contents:

#include <netdb.h>
int main()
{
gethostbyname("www.google.com");
return 0;
}

2. Then execute the following:

g++ -fmudflap (the filename you created above) -lmudflap

That will of course create an executable named a.out in the current directory. 

3. Before running, execute the following:

export MUDFLAP_OPTIONS='-internal-checking -print-leaks -check-initialization'

4. Finally, execute a.out.

Actual Results:  A barrage of memory leak information reports is printed to the console, by mudflap, finishing with the line:

number of leaked objects: 57

Expected Results:  No memory leak information should have been reported, and the final printed line should have been:

number of leaked objects: 0

Additional info:

I have tested with a fully updated Debian Sarge i386, unstable branch. The leaks reported with it are less, but still too many. They are 49.