Locating a memory leak in bash/glibc check_standard_fds()?

[David Forrest]

Dear Sir or Madam,
  I was trying the program 'memprof' on bash to experiment with memprof.  
It found a three leaks from a function 'check_standard_fds' which seems to
be a local function in glibc initialization/start code.  From hunting on
google, i found some reference to check_standard_fds as a security measure
in the startup code.  I don't know if this is a real leak, or I just don't
understand memprof, but it might be of interest to you.

Details:
memprof 0.3.0, a memory profiling tool by Owen Taylor
GNU bash, version 1.14.7(1)
libc.so.6 might be  GLIBC_2.1.3 
the memprof.leak is attached, but points at 
/usr/src/bs/BUILD/glibc-2.1.3/csu/../sysdeps/generic/libc-start.c:122

Although I'm a neophyte with memprof and memory leak testing in general,
it seems like this check_standard_fds() function could have a memory leak
that would be hard for a normal user to test or demonstrate. 

Thanks for glibc,
Dave.
-- 
 Dave Forrest                                address@hidden
 (804)296-7283h 924-3954w      http://mug.sys.virginia.edu/~drf5n/

memprof.leak
Description: Text document